Hierarchy

⤷

⤷

IMG Activity
ID | /SPE/V_RET_SPLIP | Maintain Determination of Split Profile |
Transaction Code | /SPE/79000028 | (empty) |
Created on | 20040608 | |
Customizing Attributes | /SPE/V_RET_SPLIP | Maintain Determination of Split Profile |
Customizing Activity | /SPE/V_RET_SPLIP | Maintain Determination of Split Profile |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | /SPE/V_RET_SPLIP |
Use
In this IMG activity, you can define the split profile that should be used to process messages from the SAP ICH dealer portal.
Splitting returns deliveries can result from the following scenario:
Processing messages from the dealer portal
In the portal, dealers enter the accepted quantities and the packaging information for the Return Material Authorization (RMA) items they approved. The corresponding message, submitted in the ERP system, results in the creation of a new returns delivery by partially (or completely) splitting items from the original returns delivery. The split items are usually combined into one new delivery.
Requirements
- You have already defined the suitable split profiles. To work with the dealer, at least one split profile is already defined for each message type.
- You have ensured that the split profiles are assigned to the delivery types that you are using in the returns process.
Standard settings
To complete the inbound processing of dealer portal messages, some settings related to the split profile are chosen by the system so the customizing values are not considered.
This step affects the following settings:
- Enabling a 1-to-1 delivery split (parameter V_TVDSS-NO_EMPTY_COMPLT in the general settings of the split profile)
- No deletion of zero items (parameter V_TVDSP-ZEROD in the delivery type-specific settings of the split profile)
The remaining split profile settings can be selected based on your needs.
Activities
You can maintain the used split profile based on the delivery type. Generic delivery type entries are also allowed. To use a generic type, leave the delivery type field blank. The system first looks for a delivery type-specific entry before accessing the generic entry.
Example
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | /SPE/V_RET_SPLIP | 0 | AC00000094 | Complaints and Returns |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
/SPE/V_RET_SPLIP | V - View | SM30 |
History
Last changed by/on | SAP | 20040608 |
SAP Release Created in | 100 |