Xstep V2 Gd
Elisabet Schwartzkopf
i have implemented Xstep but facing an issue while creation of process order reference Xsteps are exploded. As per Xstep practice reference Xsteps must be exploded either at the time of process order release or control recipe generation but not before if we have not set up (Set early). Could you please advise how to explode reference Xsteps automatically either at PO release or control recipe generation.
Could you please share your expert thought here how to achieve above requirement. As far as Xstep SAP file contains reference Xstep must be exploded either process order release or on control recipe generation. I could not find what wrongs goes with my configuration.
So it is not possible to suppress the explosion of SXS reference nodes in SAP standard. As described above, the explosion of SXS references happens again at the point in time when the control recipe/instruction is created. For productive control recipes/instructions it is necessary that the corresponding SXS contains an SXS version that is released and valid. Otherwise the system stops creation of the control recipes/instructions.
There might be also a constellation that a control recipe/instruction is created for a future date, but sent at a later point in time (after the future date). To prevent that SXS versions did became invalid during this time interval (future date -> after future date), the BAdI of SAP Note 2369245 can be used.
Please note that SXS reference nodes that are exploded in the master recipe/routing remain exploded (and are not re-exploded in the manufacturing order). Some customers use this feature to "freeze" the referenced content at the master recipe/routing level.
Concerning your additional question how to determine the SXS version of an SXS that is referenced in an SXS reference node: This can be established by defining custom validation symbols and creating a custom implementation for the classical BAdI CMX_XS_SRV_SYM. Unfortunately there are no appropriate validation symbols in the SAP standard namespace to archive this. The custom validation symbols then should be assigned to suited parameters at the top level (root node) of the corresponding SXS.
In general it is a very good approach to maintain the content you want to use in PI Sheets/electronic work instructions or control recipes/control instructions in Standard XSteps (SXS) that are maintained in the XStep repository (TA CMXSV). And assign them to the XStep trees of the corresponding master recipe or routing. Once the manufacturing order is created based on the master recipe/routing, the content of the XStep trees is copied. Order customizing allows you to create (productive) control recipes/instructions automatically when the order is released. In that case the system checks if SXS versions exist for those SXS that are referenced. If this is not the case, the creation of the control recipes/instructions fails. In most cases it is not necessary to manually change the XStep content in manufacturing orders.
Thank you for responding to my query. I would like to know how to explode Xstep at the time of process order release or control recipe generation but not early ? Also how to verify released xstep version at process order level ?
64591212e2