Explaining Copy Control System Settings

These steps allow you to define customer-specific copying requirement and/or data transfer routines:

1. Create a data transfer routine using custom logic (Cloud BAdI).
2. Create a copying requirement using custom logic (Cloud BAdI).
3. Define data transfer and/or copying requirement routine using Self-Service Configuration UI.
4. Set copying control: Sales document to sales document and/or billing document to sales document.

Use the Custom Fields and Logic app (user requires a role containing the catalog for Extensibility, for example SAP_BR_ADMINISTRATOR).

In a standard S/4HANA Cloud system, the app Custom Fields and Logic is included in business catalog SAP_CORE_BC_EXT (Extensibility). In a standard S/4HANA Cloud system, the business catalog SAP_CORE_BC_EXT (Extensibility) is included in business role template SAP_BR_ADMINISTRATOR.

Create a new enhancement implementation for Cloud BAdI Define Data Transfer for Sales Document Header.

Note that there are more BAdI's available in the context Sales: Sales Document, for example Define Data Transfer for Sales Document Item.

To code the custom logic:

1. Add a filter value to identify your implementation.
2. Code the relevant custom logic (in draft mode).
3. Choose Save Draft.
4. Choose Publish to activate the new custom logic.

Use the Custom Fields and Logic app (user requires a role containing the catalog for Extensibility, for example SAP_BR_ADMINISTRATOR).

Create a new enhancement implementation for Cloud BAdI Define Copying Rqmnt for Sales Document Header.

Note that there are more BAdI's available in the context Sales: Sales Document, for example Define Copying Rqmnt for Sales Document Item.

To code the custom logic use the following steps:

1. Add a filter value to identify your implementation.
2. Code the relevant custom logic (in draft mode).
3. Choose Save Draft.
4. Choose Publish to activate the new custom logic.

Use the Manage Your Solution app (user requires a role containing the catalog for End to End Implementation Experience - Implementation Cockpit, for example SAP_BR_BPC_EXPERT).

In a standard S/4HANA Cloud system, the app Manage Your Solutionis included in the business catalog SAP_CA_BC_IC_LND (End to End Implementation Experience - Implementation Cockpit). In a standard S/4HANA Cloud system, the business catalog SAP_CA_BC_IC_LND (End to End Implementation Experience - Implementation Cockpit) is included in business role template SAP_BR_BPC_EXPERT.

Choose Sales Application Area, Sales Order Management, and Processing Sub Application Area.

Choose the Copying Control for Sales Documents item.

Choose Configure for step Define Data Transfer and Copying Rqmts for Sales Documents.

Add two new entries, one for a copying requirement and the other for a data transfer routine as follows:.

1. Select Process Enhancement Option SD_SLS_COPY_RQMT_HEAD_SLS (Copying Requirement - Sales to Sales (Header)).
2. Enter a number in the Routine Number field between 3000000 and 3009999.
3. Enter a meaningful Routine Description.
4. Repeat the steps above for SD_SLS_DATA_TRANSFER_HEAD (Data Transfer for Sales Document (Header)).

For each of the new entries, navigate to the second level Assign Enhancement IDs to a Routine Number and complete the following steps:

1. Choose New Entries.
2. Select the relevant process enhancement option (only one is available!).
3. Enter the filter value you have created in the previous step and save the data.

The SSCUI can be found in the application area: Sales, and the sub application area: Sales Order Management and Processing.

In the Sales Order Management and Processing sub application area, select Copying Control for Sales Documents.

Select the applicable configuration step depending on whether the configuration is added for copying to a sales document or a billing document.

Select the Header level and then select the combination representing the applicable source and target documents.

Enter the routine numbers you have created in the Add Routines Step into the Data Transfer and/or Copying Requirement fields.