Enhancement CAVC0000 - External API's
Function group XCAVC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCAVC_CFG_001 | ZXCAVCU01 | Provide Customer Enhancements to BOM Item |
EXIT_SAPLCAVC_INST_001 | ZXCAVCU02 | Provide Customer Enhancements to BOM Item |
EXIT_SAPLCAVC_INST_002 | ZXCAVCU03 | Set Customer Enhancements to BOM Item |
In the application system, user-defined fields can be added to the item data of the bill of material (BOM). For this purpose, the structure CI_STOP is defined in the ABAP Dictionary. The user-defined fields are part of individual structures that are transferred to the API interfaces. User exits are provided to read and write data within the APIs. All user exits are grouped in the function group XCAVC and have a uniform structure.
o There is no error handling
o Each user exit handles only one single item
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CEI00000 - Availability of Customer Functions in Configuration Editor
Function group XCEI0
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEI0_001 | ZXCEI0U01 | SD Customer Fields in a Configurable Instance |
EXIT_SAPLCEI0_010 | ZXCEI0U02 | Customer Pushbutton 01 |
EXIT_SAPLCEI0_011 | ZXCEI0U03 | Customer Pushbutton 02 |
EXIT_SAPLCEI0_012 | ZXCEI0U04 | Customer Pushbutton 03 |
EXIT_SAPLCEI0_013 | ZXCEI0U05 | Customer Pushbutton 04 |
EXIT_SAPLCEI0_014 | ZXCEI0U06 | Customer Pushbutton 05 |
EXIT_SAPLCEI0_015 | ZXCEI0U07 | Customer Pushbutton 06 |
EXIT_SAPLCEI0_016 | ZXCEI0U08 | Customer Pushbutton 07 |
EXIT_SAPLCEI0_017 | ZXCEI0U09 | Customer Pushbutton 08 |
EXIT_SAPLCEI0_018 | ZXCEI0U10 | Customer Pushbutton 09 |
EXIT_SAPLCEI0_019 | ZXCEI0U11 | Customer Pushbutton 10 |
Many customers would often like the option to jump from the configuration editor to their own interfaces and functions to complete the configuration process accordingly. This desired function may relate only to the configurable product. Therefore, the solution should be a modelling option and not a modification carried out in the usual way.
You can design the interface using the interface design in relation to a product or a configuration profile. In the context of this interface design, you can position and group characteristics as you wish. You can form the characteristic group using a pushbutton. The customer can define the name of the pushbutton himself. If you choose the pushbutton, then a modal window is displayed where the characteristics are presented according to the modelling. Using the current system, the customer can activate up to 10 characteristic groups using the freely definable pushbuttons. The pushbuttons are displayed vertically and on the right next to the characteristic value assignment.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUCEI0B - Customer-Specific Batch-Input Processing
Function group XCEI0
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEI0_020 | ZXCEI0U12 | Switch Off Standard Batch-Input Screen 0109 |
The user can use this user exit to deactivate the standard batch input screen 0109 in the function group CEI0 and to use the self-written editing of the batch input. In this case, the export parameter USER_BATCH_INPUT must be set with the value 'X'.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUCEI0A - Assigned Values Files and Object Characteristics
Function group XCEI0
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEI0_021 | ZXCEI0U13 | Assigned Values Files and Object Characteristics |
The customer enhancement does not allow object characteristics to be stored. You have the following situation when this customer enhancement is not used in the assigned values file:
The KMAT is valuated in the configuration. The characteristics are saved in the corresponding storage location. However, if object characteristics are valuated and stored and KMAT is ordered again with another quantity in the same document for example, and the value assignment from storage is used, then the object characteristics are overwritten and the document contains the wrong quantity (object characteristics from storage). This customer enhancement is used if you do not want to use object characteristics from storage for the current value assignment.
Prerequisite
The export parameter OBJECT_CHAR_NO_LIBRARY in the function module exit_saplcei0_021 must be set.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUCEI0H - Change F4 Help for Characteristics in the Configuration
Function group XCEI0
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEI0_022 | ZXCEI0U14 | Change presentation of F4 help |
You can manipulate the F4 help for the values on the value assignment screen. This means that you can change the contents of the F4 help. For example, you can specify that certain values that are invalid on certain days (or similar) cannot be transferred (as in change management). You receive a table in the enhancement that contains all information about the existing values and you can maintain the following parameters (for example) in this table also:
o Additional values can be specified and transferred
o The values is displayed but cannot be transferred
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUCEI0V - Search for Material Variant with Same Values
Function group XCEI0
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEI0_023 | ZXCEI0U15 | Activate Search for Material Variant with Same Values |
The export parameter 'Type_Check' must be set. If you set 'W' (warning) and at least one material variant is returned, the system issues a warning and saves the material variant upon confirmation. If you set 'A' (termination) and at least one material variant is returned, the transaction terminates and the material variant cannot be saved. If you set another symbol or none at all, the check is not carried out.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0100 - Synchronization of Variant Configuration Initialization
Function group XCUI
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUD0_003 | ZXCUIU01 | Time of Initialization for Variant Function Program Environment |
When you use variant functions, these functions have global data. You can use this customer enhancement to initialize these global data areas, for example when saving a sales order or during the material requirements planning run (MRP) to release the relevant occupied storage space.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUP0001 - Reporting - planning tables
Function group XCUP
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUD2_800 | ZXCUPU02 | Check reporting - planning tables |
EXIT_SAPLCUTS_800 | ZXCUPU01 | Reporting - planning tables |
You can use the customer enhancement CCUP0001 to report planning tables with your own ABAP source code. The customer exit EXIT_SAPLCUTS_800 is used to mark planning tables that are not reported by default. You can use the customer exit EXIT_SAPLCUD2_800 to report the planning tables with your own ABAP source code.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0510 - Konfiguration: Zusatzverarb. Änderung Inhalt Variantabelle
Function group XCUT
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUD3_001 | ZXCUTU02 | Configuration: Additional Processing When Changing Variant Table Entries |
After you change a variant table, customer-specific additional processing can be triggered by the user exit.
Prerequisites:
o Variant tables are used (transaction CU60).
o The runtime object for the variant table must also be activated. This can occur in the maintenance transactions for the structure in the variant table in the menu path "Extras -> Runtime Object -> Activate".
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0001 - Load functions for configurations
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUD0_001 | ZXCUCU01 | Configuration Decision to Load Configuration from External Source |
EXIT_SAPLCUXC_001 | ZXCUCU03 | Load Configuration from External Source |
You can use this enhancement to load configurations from external sources, for example from the SAP R/2 stand-alone configurator.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0000 - Additional Check for Configurations
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUKO_001 | ZXCUCU02 | Additional Check on Configuration |
This enhancement lets you transfer control of the configuration to a customer-specific program after maintenance. The configuration can be checked. If the configuration is incorrect or incomplete, then the exception INCONSISTENT_CONFIGURATION is triggered.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0002 - Reaction for conflict in object search on class node
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUD0_002 | ZXCUCU04 | Reaction Option to Conflicts When Finding Objects in Class Node |
If a conflict situation arises during the object search for a class node, this user exit receives the control and may be able to solve the conflict. A conflict occurs if
o No object is returned but at least one object is always required. If a class item has to be replaced by a component but no object is returned, the user exit can be used to select, for example, a material with the corresponding classification.
o Several objects are returned but only one object is allowed. If only one component can be transferred but several objects are returned during the object search, the user exit can be used to determine which object is to replace the class item.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0800 - Level of Detail of Multi-Level Explosion in Configuration
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUKO_002 | ZXCUCU05 | Level of Detail of Multi-Level Explosion in Configuration |
The enhancement CCUX0800 allows you to use the function module EXIT_SAPLCUKO_002 as an enhancement component. By setting the parameter EXPLODE_ALL = 'X', you are able to explode all assemblies. If you want to explode only the configurable assemblies, set the parameter EXPLODE_CONFIGURABLE = 'X'. If you do not set the parameters or do not use the enhancement, then only the configurable assemblies that can also have a characteristic value assignment are exploded.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0004 - Post-Processing of Configuration with Dependencies
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUKO_003 | ZXCUCU07 | Post-Processing of Configuration |
This enhancement allows you to make further changes with object dependencies after the configuration has been completed. After the customer exit has been called, the configurator takes the value changes into account. The enhancement can be used for SUM_PARTS for example.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUXINST - Modification for External No. Assignment for Instantiation
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUKO_004 | ZXCUCU09 | Instantiation Parameters |
In the result-oriented order BOM, only one explicit material number assignment is possible for the instantiation. This is possible only for the selected item in top-down or bottom-up instantiation. All other items contain an internal material number. In the function module EXIT_SAPLCUKO_004 of the customer exit, you can maintain the material number, material type, industry sector, template material and material short text. Similarly, you can determine whether number assignment should always run in the background or whether the values should be available as default values for entry.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0005 -Transfer of Item Category by Type Matching
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEB1_001 | ZXCUCU10 | Transfer of Item Category After Replacing KMAT with a Variant |
In some cases, the item category may not be retained in type matching for a configurable material in the result screen of the configuration. You can use this customer enhancement to control which item category is to be chosen for type matching in the order BOM.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUXSETM -Saving of Manual Changes for SET Processing
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUKO_005 | ZXCUCU11 | Save Manual Changes for Scenario Sales Order (SET) |
EXIT_SAPLCUKO_006 | ZXCUCU12 | Import Manual Changes for Scenario Sales Order (SET) |
This enhancement allows you to save and load manual changes in the BOMs on the result screen of the configuration in the sales order scenario (SET). The indicator "Manual Changes Allowed" must be set in the configuration profile. The enhancement allows you to make changes in a consistent way in both the BOM master data (transaction cs02) and in the BOMs on the result screen of the interactive configuration (transaction va01 or va02).
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0006 - Fixing of an Order BOM
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUKO_007 | ZXCUCU13 | Exit to "Correctly" Fix an Order BOM |
When you process order BOMs in the configuration, interim changes to a material BOM are dynamically transferred to the order BOM. This customer enhancement does not allow the dynamic "merging" of changes in the material BOM with the order BOM.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0007 - Definition of BOM Category for Instantiation
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEB1_002 | ZXCUCU14 | User Exit for Definition of BOM Category for Instantiation |
You cannot influence the BOM category during instantiation. However, this customer enhancement does allow you to influence the BOM category of a material to be instantiated.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUX0008 - No BOM Explosion for Externally Procured Components
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUKO_008 | ZXCUCU15 | No BOM Explosion for Externally Procured Components |
The BOM explosion for externally procured components is suppressed in a multi-level variant configuration. There are no business reasons for this. This is done to save performance in the explosion. The customer exit EXIT_SAPLCUKO_008 allows you to suppress the explosion for externally procured components in order to improve performance.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancment CCUXSTAT - Define BOM Status for Instantiated Materials
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEB1_003 | ZXCUCU16 | Define BOM Status for Instantiated Materials |
When a material is instantiated, a BOM is also created for this material. This BOM receives the default BOM status from Customizing. This is also true for the order BOM. The default status from Customizing is provided for BOM creation in the dialog. It does not necessarily make sense to transfer this status for instantiated materials or order BOMs. If a material is instantiated, then a BOM (among other things) is also created for this material. This customer enhancement allows you to determine the status of the new BOM. If this enhancement is not activated or the output parameter is not filled, then the default BOM status is transferred from Customizing.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhanchement CCUX0003 - Parameterization of Finding Objects in Class Node
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEIS_001 | ZXCUCU17 | Parameters for Finding Objects for Class Item Finding Objects for Class Item |
This enhancement is used to control the automatic object search when a class node is replaced. In the standard system (without this enhancement), the search in the class returns only those objects whose value assignment for the selection-relevant characteristics exactly matches the search variants. This enhancement also allows objects to be found for which search-relevant characteristics are not valuated. You can choose the search type in the function EXIT_SAPLCEIS_001 using the class, class type and the object type.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUXOBTY - Object Types for the Object Search for Class Nodes
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEIS_002 | ZXCUCU19 | Object Types for the Object Search for Class Nodes |
The enhancement CCUXOBTY is used to control the object search when class nodes are replaced. The type of objects to be found can be determined here. The enhancement should only be used in the material search. You can control the object search so that material variants can also be found due to their configuration value assignment. In the standard system, material variants can be found only if, apart from the configuration, they are assigned via the usual classification of the class and are valuated accordingly. The object types are marked with the following constants: MARA: Classified materials (classified material variants also) MARC: Configuration of plant-dependent material variants MARAT: Configuration of cross-plant material variants.In the function EXIT_SAPLCEIS_002, the variable CV_OBJECTTYPE or the table CT_OBJECTTYPES can also be filled depending on whether only one object type (CV_OBJECTTYPE) or several object types (CT_OBJECTTYPES) are to be allowed.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancment CCUXMVAR - Multistep Configuration with Material Variants
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUKO_009 | ZXCUCU20 | Multistep Configuration with Material Variants |
The function module EXIT_SAPLCUKO_009 enables the multi-level configuration of material variants.
Export parameter:
EV_MULTILEVEL Multilevel BOM Explosion
For material variants to have multi-level configuration, the export parameter EV_MULTILEVEL has to be filled with 'X' when you leave the module.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUXDYNP - Dialog for Incomplete Assigned Characteristic Values
Function group XCUC
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUKO_011 | ZXCUCU21 | Dialog for Incomplete Assigned Characteristic Values |
When you use the customer enhancement CCUX0001 (Load functions for configurations), you cannot branch to screen 1005 (function group CUKO) when you have incomplete assigned characteristic values. The customer enhancement CCUXDYNP allows you to control the call of screen 1005 when loading functions from an external source.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUXDATU - Explosion Date for Result-Oriented Order BOM
Function group XCUC1
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCASL_001 | ZXCUC1U01 | Explosion Date for Result-Oriented Order BOM |
This customer enhancement allows you to influence the explosion date of the order BOM structure in order BOM processing (transaction CU51E). This date is applied to the explosion of the entire structure and cannot be changed for each assembly.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUXIACD - Maintain Additional Data for Instantiation
Function group XCUC1
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCEB1_100 | ZXCUC1U02 | Maintain Additional Data for Instantiation |
In order BOM processing (transaction CU51E), you can create material variants with a related BOM via instantiation. Data of a template material is copied here. You may have to transfer additional data (task list, cost collector, and so on) depending on the scenario.This SAP enhancement can be used to maintain additional data when saving an instantition.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUXDATE - Validity Date for Order BOM
Function group XCUC1
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCASL_002 | ZXCUC1U03 | Validity Date for Order BOM |
You are using backward scheduling in requirements planning. If the determined start date lies in the past, you must ensure that a valid sales order BOM exists at the start date. To ensure that an order BOM is also valid in the past, enter a "Valid from" date that lies before the specified start date when you create or change the sales order BOM. The system proposes the system date as the "Valid from" date by default. This customer enhancement CCUXDATE enables a different validity date from the system date to be proposed when you branch to sales order BOM processing.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CUCPDELE - Additional Logic Delete Classification Data from LO-VC View
Function group XCUCP
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCLDL_002 | ZXCUCPU01 | Ignore Selected Objects When Deleting in CLDL |
EXIT_SAPLCUCP_003 | ZXCUCPU02 | Delete assignment of characteristic to class despite configured object |
EXIT_SAPLCUCP_004 | ZXCUCPU03 | Deleted Assignment of Class to Object Despite Configured Objects |
EXIT_SAPLCUCP_005 | ZXCUCPU04 | Delete assignment of profile to object despite configured objects |
This customer enhancement allows you to deviate from the standard system settings when deleting configuration profiles, class and configuration data for configured objects.
You can delete
* Configuration profiles
* Class assignments to objects (material) and
* Characteristics from classes
even if there are configured objects (sales orders for example) for this object (material).
Furthermore, you can avoid deleting the value assignments (AUSP entries) for the affected configured objects (sales orders for example) if a characteristic is deleted from a class. This is required to keep the "old" configured objects consistent.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CUCPDEL1 - Additional Logic:Delete Classification Data LO-VC View CBASE
Function group XCUCP
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUCP_006 | ZXCUCPU05 | Delete Assignment of Characteristic to Class Despite Configured Obj. CBASE |
EXIT_SAPLCUCP_007 | ZXCUCPU06 | Delete Assignment of Class to Object Despite Configured Object CBASE |
EXIT_SAPLCUCP_008 | ZXCUCPU07 | Delete Assignment of Profile for Object Despite Configured Object CBASE |
This customer enhancement allows you to deviate from the standard system settings when deleting configuration profiles, class and configuration data for configured objects.
You can delete
o Configuration profiles
o Class assignments to objects (material) and
o Characteristics from classes
even if there are configured objects (sales orders for example) for this object (material) in the new configuration storage (CBASE).
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CUCQ0001 - Additional Logic: Selection of Confign Profiles (in FG CUCQ)
Function group XCUCQ
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUCQ_001 | ZXCUCQU01 | Additional Logic for Selection of Configuration Profiles in FG CUCQ |
This customer enhancement allows you to deviate from the standard system settings when selecting configuration profiles. You can restrict the number of valid configuration profiles. If the number of configuration profiles is reduced to one, then a manual selection is no longer made. If the number of configuration profiles is reduced to zero, then this configurable material is deemed not configurable. (No instance is generated). You can still specify whether the configuration profile is to be manually selected. Note the following: The configuration parameters (fields) of the individual configuration profiles may never be changed.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCUXSETQ - Component Quantities for Set Handling
Function group XCUC2
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCUKO_010 | ZXCUC2U01 | Control: Quantity Comparison Yes/No |
You can use the enhancement CCUXSETQ to ensure that the newly calculated quantity is also used for different component quantities in relation to the sales order and the new BOM explosion and that this can still be changed by object dependencies in further processing. This behavior can be controlled depending on the import parameters
o iv_matnr Material number of the initial material
o iv_plant Plant
o iv_quantity Quantity of initial material
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Enhancement CCLD0001 - Extension of the IDoc for ALE Message Type CNPMAS
Function group XCLD
User Exit | Include | Description |
---|---|---|
EXIT_SAPLCLD1_001 | ZXCLDU02 | Fill the Customer-Specific IDoc Structures for CNPMAS |
EXIT_SAPLCLD1_002 | ZXCLDU03 | Read the Customer-Specific Enhancements from CNPMAS |
EXIT_SAPLCLD1_003 | ZXCLDU01 | Update of Data Imported by User Exit by ALE |
This enhancement allows you to process additional segments in the IDoc for the ALE type CNPMAS. An IDoc enhancement must be manually extended to include the customer-specific segment for the function of this user exit.