Ansicht
Dokumentation

CRMV_IO_PROC_MA - Define Follow-Up Transaction Types for Interaction Object

BAL_S_LOG - Application Log: Log header data   General Material Data  
This documentation is copyright by SAP AG.

In this activity you define which business transactions can be used in the transaction history as follow-up transactions for interaction objects (IO). To do this, first add the transaction type you require. Only the transactions that belong to the transaction types can be generated as successors to the IO (in application Activities).

In the second stage of Customizing you define how the business partner of the interaction object is transferred to the follow-up transaction. Because the IO, unlike business transactions such as the activity, does not possess any partner functions, the usual copy control by the partner functions cannot be used.

For this reason, you must define how business partners of the type Person or Organization are transferred to the partner functions of the follow-up transactions. Both B2B and B2C scenarios are taken into consideration (see example).

1. Choose New Entries and use the F4 help to select the transaction type you want to use.
2. Save your entries. A name and description are automatically added to the transaction type.
3. Double-click the node Select Business Partner Type and select the desired business partner type.
4. Double-click the node Assign Business Partner to Partner Functions.
5. Choose New Entries and select the desired partner function using the F4 help.
6. Save your entries.

The following examples show how the partner functions are transferred to the follow-up transactions using an activity of type Contact with the usual partner functions activity partner and contact person:

• B2C Scenario: The 'recipient' of the IO is a person. This person should be transferred to the follow-on activity as an activity partner and contact person. In the second stage of this activity, choose the entry Partner functions if recipient = Person and in the third stage select the partner functions activity partner and contact person.

• B2B Scenario without contact person: The organization is contacted directly and is thus entered in the 'recipient' field of the IO. In this case, the function activity partner must be selected for the entry partner functions if recipient = organization in the third stage. The contact person is determined by the internal partner determination of the business transaction.

• B2B scenario with contact person: A contact person within an organization is contacted. The organization occupies the field Organization and the person the field Recipient in the IO. Assign the function activity partner to the entry Partn. Fct. for Org. ('Recipient' & 'Organization' Filled). Assign the function contact person to the entry Partn. Fct. for Person ('Recipient' & 'Organization' Filled).

BAL_S_LOG - Application Log: Log header data   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 3863 Date: 20240523 Time: 175809     sap01-206 ( 80 ms )