Hierarchy
SAP_APPL (Software Component) Logistics and Accounting⤷
LO-ARM (Application Component) Advanced Returns Management⤷
MSR_SD (Package) Multi-Step Returns: SD Enhancements
IMG Activity
| ID | MSR_SD_SALES | BAdI: Change Returns Data and Billing Block in Returns Order |
| Transaction Code | S_E4A_94000260 | (empty) |
| Created on | 20080627 | |
| Customizing Attributes | MSR_SD_SALES | Change Returns Data and Billing Block in Returns Order |
| Customizing Activity | MSR_SD_SALES | Change Returns Data and Billing Block in Returns Order |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | MSR_SD_SALES |
Use
This Business Add-In (BAdI) is used in the Advanced Returns Management (LO-ARM) component. The Sales Orders (SD-SLS-SO) component is also affected.
You can use this BAdI to change or automatically enter returns-specific data in a returns order in Advanced Returns Management during user interaction and to set the billing block at header or item level taking returns-specific data into account.
This BAdI is optional.
Requirements
Standard settings
In the standard system, there is no activated BAdI implementation.
This BAdI is designed for multiple use. All activated implementations are called and executed.
The BAdI is not filter-dependent.
Activities
Create a BAdI implementation for BAdI MSR_SD_SALES of enhancement spot BADI_SD_SALES_ITEM.
For information about implementing BAdIs as part of the Enhancement Concept, see SAP Library for SAP NetWeaver under BAdIs - Embedding in the Enhancement Framework.
Example
You can check whether a batch recall exists for the material and set the return reason accordingly.
You can set the follow-up activity code and data related to this follow-up activity automatically based on customer-defined business rules. For example, if certain materials must always be shipped to the vendor for inspection, you can set follow-up activity Ship to Vendor and enter the vendor number. Another example is when you want to scrap certain materials below a certain value if the returns reason says that the material is damaged.
You can set the inspection code to a default value if inspection is not relevant in certain return scenarios, for example, when the return reason indicates a buyback of materials in their original packaging.
You can set the refund control according to the follow-up activity. For example, if the follow-up activity is Ship to Vendor, you can set the refund control to A After Receipt of Credit Memo.
You can set the returns refund code according to your business rules. Usually in a buyback scenario, you set a refund code that includes a restocking fee when the customer returns materials after a certain period calculated from the original sales date. You can also consider different periods for different customer groups.
You can set the billing block at item level or at header level if the refund amount of an item or for the whole returns order exceeds a certain amount.
See Also
This BAdI uses interface IF_EX_MSR_SD_SALES. For more information, display the interface in the Class Builder.
When new returns order items are created, the method CHANGE_RETURN_DATA (Change Returns Data) of this BAdI is correlated with method GET_DEFAULTS (Get Default Values for Returns Data) of BAdI MSR_TRC (Configuration of Settings and Checks for Returns Data).
Business Attributes
| ASAP Roadmap ID | 257 | Create User Exits |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-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 | MSR_SD_SALES | 0 | E4A0000031 | Advanced Returns Management |
Maintenance Objects
| Maintenance object type | E | Business Add-In - Definition |
History
| Last changed by/on | SAP | 20080814 |
| SAP Release Created in | 604 |
