top of page

Vetacad Group

Offentlig·3 medlemmar

Sap Configuration Of Serial Number Incompatible With Document Item |WORK|

It is not possible to replace a class item with more than one object. 'Multiple selection flag' only means that all the objects are shown in the result screen (This Only applies to Profile SET/ORDER BOM with Flag 'Manual changes allowed' ticked) however it is only replaced by one component. Note 438683 describes the functionality of the flag. Usually when more than one item is found, the first one (or the last one) is used to replace the class node. User exit CCUX0002 allows you to influence this behaviour, but does NOT enable you to replace the class with multiple objects. It only finds all the objects which fulfill the condition and you can then define in your coding which item to select. Eg if you find material A, B and C, you can write your own coding in the User-Exit to choose B instead of A. More information on the exit can be found under the documentation of the Exit.

sap configuration of serial number incompatible with document item

This message appears if configuration of the serial number and configuration of the position are not the same. First we need to find out which configurations are been compared. For that you can set a breakpoint here:

Here you can see with which instances the function module is been called (P-CUOBJ, EQUI-CUOBJ). The function returns sy-subrc = 1 if the configurations are different. Once you have got the instances being compared you can use report RCU_COMPARE_CONFIGURATIONS to find out the differences between the 2 configurations. If a material variant is been involved it might help to save the configuration of the material variant again. This could help if the configuration model (e.g. dependency) had been changed, therefore new values been derived for the variant, but the configuration of the variant not been saved after the change. With Report RCU_EXCL_CHARACTERISTICS (see note 901610) characteristics can be excluded during the type matching and/or during the comparison of the configuration results of serial number processing. If this report is been executed for the characteristics with different values those characteristics are not taken into account for comparison anymore.Breakpoints:CEI0_COMPARE_CONFIGURATIONS

When a customer calls the service hot-line with their serial number, the customer service representative will look up the serial number status in SAP which indicates whether that s/n is under warranty or not and what type of service is covered for that part and customer. Is it under warranty or contract? By maintaining serial number history, SAP can help to know what product service is covered and what can be offered as an up-charge?

RMA,- Return Material Authorizations, are easier said than done. Whether the issue occurred after order taking, while the unit is being picked and packed, during shipping, immediately after receipt, DOA, issues with the material, or at a later time: Make the customer whole and a happy customer is your best business objective. Think about Amazon Returns - does Amazon record serial numbers? Amazon usually only records serial numbers for larger valuable items they have total control over, sell and ship themselves, and items of very high value. That's why 3rd party sellers normally perform their own fulfillment if what they sell should have a serial number applied at the time of shipping, which allows them to apply the s/n during the sale and shipping, thus record and track serial numbers.

The equipment record is where a lot of the serial specific data lives. The equipment record has a system-wide unique ID, the Equipment Number. The equipment number is tied to the material and serial number combination. This is a great concept to leverage within your company. For some manufacturers, a given serial number is unique and sufficient to identify a unique part.

By printing the equipment number on the equipment tag in combination with all the usual data: Such as corporation / manufacturer name, address, phone number, material, serial number, country of origin, certain disclaimers, instructions, etc.

Although 2D bar codes require image processing software, typically integrated to the bar code scanner, they are superior to simple barcodes because they have many traceability advantages, and read-error recognition capability. 2D codes assist in tracking for example automotive parts during manufacturing and through aftermarket service. In Aerospace and Medical industries serial number tracking is done for decades. With SAP, you can employ the same concepts in your industry with a relatively low barrier of entry.

By employing that simple hack, using the equipment number as the key record locator, you are enabling reliable serial number look up by anyone with access to the equipment database. Access by way of using SAP apps, mobile apps, SAP Fiori integrated in your Customer Service Portal. SAP Fiori works across all device types.

Current and future naming standards are important in maintaining your SAP serial number history. This allows a serial number to be a 'speaking' serial number, meaning, you can track changes all the way back to the beginning of the part's existence. What are the recommendations in SAP with regards to Serial Number design and are you following them? Are there industry naming conventions you must follow. Are they Milspec (Military Specification) or Automotive Industry compliant?

When a vehicle leaves the industry, it is identified by a 17-character number (Vehicle Identification Number, VIN) which is on its title, and referred to in all official documentation, such as the registration, insurance, smog checks, notifications of government agencies, etc. Various components of the vehicle are also serialized, during its assembly: a standard serial number makes each major vehicle part unique and traceable.

Often times, for example, in Aerospace and Defense, part and serial numbers are controlled via engineering orders (USAF calls it TCTO or Time Compliance Technical Orders) which requires that we do something to the item in question. Which in turn, makes it a new part or serial number.

[Definition: A final result tree is a result tree that forms part of the output of a transformation: specifically, a tree built by post-processing the items in the principal result or in a secondary result. Once created, the contents of a final result tree are not accessible within the stylesheet itself.] Any final result tree may be serialized as described in 26 Serialization.

In previous releases of this specification, a single node was typically supplied to represent the source document for the transformation. This node was used as the target node for the implicit call on xsl:apply-templates used to start the transformation process (now called the initial match selection), and the root node of the containing tree was used as the context item for evaluation of global variables (now called the global context item). This relationship between the initial match selection and the global context item is likely to be found for compatibility reasons in a transformation API designed to work with earlier versions of this specification, but it is no longer a necessary relationship; the two values can in principle be completely independent of each other.

The value given to the global context item (and the values given to stylesheet parameters) cannot be nodes in a streamed document. This rule ensures that all global variables can freely navigate within the relevant tree, with no constraints imposed by the streamability rules.

In previous versions of XSLT, results were delivered either in serialized form (as a character or byte stream), or as a tree. In the latter case processors typically would use either their own tree representation, or a standardized tree representation such as the W3C Document Object Model (DOM) (see [DOM Level 2]), adapted to the data structures offered by the programming language in which the API is defined. To deliver a raw result, processors need to define a representation not only of XDM nodes but also of sequences, atomic values, maps and even functions. As with the return of a simple tree, this may involve a trade-off between strict fidelity to the XDM data model and usability in the particular programming language environment. It is not a requirement that an API should return results in a way that exposes every property of the XDM data model; for example there may be APIs that do not expose the precise type annotation of a returned node or atomic value, or that fail to expose the base URI or document URI of a node, or that provide no way of determining whether two nodes in the result sequence are the same node in the sense of the XPath is operator. The way in which maps and functions (and where XPath 3.1 is supported, arrays) are returned requires careful design choices. It is recommended that an API should be capable of returning any XDM value without error, and that there should be minimal loss of information if the raw results output by one transformation are subsequently used as input to another transformation.

The sequence normalization process either returns a document node, or raises a serialization error. The content of the document node is not necessarily well-formed (the document node may have any number of element or text nodes among its children).

If there is no item-separator, then a single space is inserted between adjacent atomic values; for example if the raw result is the sequence 1 to 5, then sequence normalization produces a tree comprising a document node with a single child, the child being a text node with the string value 1 2 3 4 5.

If there is an item-separator, then it is used not only between adjacent atomic values, but between any pair of items in the raw result. For example if the raw result is a sequence of two element nodes A and B, and the item-separator is a comma, then the result of sequence normalization will be a document node with three children: a copy of A, a text node whose string value is a single comma, and a copy of B.


Welcome to the group! You can connect with other members, ge...
bottom of page