Execute Backorder Processing

I've seen a lot of Q&A session on the backorder processing and rescheduling and would like to discuss the backorder processing in this blog and would write up a follower for rescheduling.

Backorder processing as the name specifies is allocation and confirmation of quantity that has NOT been confirmed to a customer order prior, mainly due to absence of stock. Using Backorder processing, we could also override the quantities confirmed via "Product Allocation".

Rescheduling on the other hand is to remove already confirmed quantities of a customer order and reallocate it to another priority customer, which could also be due to shortage of stock  .

Note: The key configuration necessary for Backorder processing is the “Checking Rule for Updating Backorders”. The checking rule is determined based on the availability check maintained in the Material Master – Sales/General Plant tab per client requirements.

1.      Execute Transaction Code V_RA – Backorder scheduling. Note below that the cumulative confirmed quantity is Zero for both orders.

2. Both Orders are open and not blocked

3.  Select the line which want to allocate and confirm quantities. We could also select all the lines by clicking “Select all” button.

4. The selected line will be in blue in the below screen. Select the line and Click “Change Confirmation" at the top.

 5.      Enter the quantity you want to confirm in the ‘Committed” field at the bottom left screen.

Note: Click on the Back icon on the screen and the system will prompt to “Copy the confirmation” and Click the Yes button.

      6. On Clicking the Yes button, the confirmation quantity is copied to the order line. Note the cumulative confirmed qty has been changed to 20.

7.   Open the order and check the schedule lines, and you should notice the order has been for 72 qty and confirmed for 20. The remaining 52 qty will still be on backorder.

Sales - Sales org 2 View: Activate Material Groups 1 – 5

TCode OMSR: The Field selection group is assigned to each field

     

TCode OMS9

Enter Field Select Group = 54 and hit Enter

Select “by field Selection” in the Sort Entries at the bottom left corner

Select Radio Optional for TCodes MM01, 02 & 03

Attach external documents to SD Documents

Requirement: Attached external files (Word/PDF/xls) to SD related documents like Customers, Sales Orders, Deliveries or Billing Documents.

Pre-requisite: Use TCode SU3 to assign and set parameter ID SD_SWU_ACTIVE to X.

SD_SWU_ACTIVE

Solution: There are two ways to navigate in the Document screen and see screens below to attach files and note that the file can only be attached in the Change Display mode and NOT in Create mode.

Option-1

Option-2

Regards

[V]

Product Allocation : Product allocation check found changes to the confirmation

Issue :  Product allocation check found changes to the confirmation and the confirmation quantity is 'Zero'.

Solution : This issue occurs if a custom info structure is created with characteristics other than that of the standard product allocation structure S140. In such case, program User_Exit FV45VFZY, Include  USEREXIT_QUOTA_KEY_VALUE to pass custom characteristics from LIS to be filled and pass to internal LIS structure.

I have a Custom info structure created and notice from the above debug screen that the Material group and Material number fields are not filled. With appropriate code in place fill the custom fields to pass data to MCVBAP (LIS Item level info structure). The data from  these structures performs a check against the SXXX structure maintained for product allocation and confirms the quantities. 

S4 HANA Customer Master Sales Area Data - Changes to BP are not saved

Issue

Changes to BP are not not saved when we extend the BP data to Sales Area even though you see the message "Changes have been saved" without any other error message. However, if you open the BP again, you will notice that the changes actually are not saved to database.

Cause

What I noticed is that if there are some mandatory fields that are required to save the data, but there are no errors are displayed during the 'Save' of the document.

Resolution

1. Execute TCode MDS_PPO2.

2. Input the Technical Creation date (date you actually performed the changes) in the selection screen.

3. Check if there is any error in the PPO log. If there is error, please correct them then perform the change on BP again.

Source : SAP

Service Order Material Bill of Material Explosion - Components Tab (IW31/IW32)

Requirement: 

• Display the list of components required/relevant for an equipment in a repair service Order

Solution: 

• Use TCode CS01 to create a Bill of Material with Usage-4 (Plant Maintenance).
• During the creation of the Service Order (IW31/IW32), Click the 'Operations' Tab, and then click the General tab and bottom left of the screen.
• Enter the BOM material created from CS01 in the 'Assembly' field and hit Enter.
• Click the 'Assembly' Icon to the bottom of the Screen.

SAP Sales Rebates vs Vistex Sales Rebates (Sales Rebates)

Below are a few differences between SD rebates and Vistex, Vistex has evolved over a period of time and the product has matured based of organizational requirements unlike SD rebates is at a stand still.

In short, SD Rebates can be implemented for organizations for simple rebate processing and low document volume, whereas Vistex handles complex business processes with very high data volumes.

Processes	SAP Rebates	Vistex
Flat Rebates	Handles simple and straight forward requirements. Simple to Configure and Maintain Tracking is very easy Partial settlement Possible by default	Medium level configuration but provides multiple called transnational model options and screens for additional maintenance. Tracking is also simple but complex config. Additional config to handle Partial settlements
Scales or Tier Based	Limited functionality where accrual is per document No functionality exists for volume, growth or target based rebates	Complex, called composite model and can handle excellently Examples include growth based, volume based,target based rebates The most robust feature of Vistex and complex maintenance on the other hand.
Rebate Recipient	Payment to only one recipient	Payments can be made to multiple recipients
Reports	Limited functionality Customer reports for specific requirements	Standard reports available Customer reports for specific requirements Vistex provides standard BI extractors
Accrual Process	Easy to trouble shoot	Complex
Retroactive	Execute a report to correct data	Implement a functionality to handle retroactive rebates. Process the invoices for subsequent IP processing
Accrual Postings	Posting to FI based on service rendered date	Posting to FI on billing date
Currency Conversion	Posting based on service rendered date by default	Posting based on billing date
Credit Memo generation	Creates SD billing document by default.  Payments made only to recipient which is normally a customer	Default config to create direct FI invoice Custom development to process for SD billing.  Can make payments to customer or Vendors as per business requirements via config.
Re-process documents	Cannot re-process/change once billing document has been created	Easy to troubleshoot Can reverse FI postings like accruals mainly and re-price/re-create documents
Exclusions	No material or customer exclision from group if rebates maintained at group level	Handled by standard configuration
Customer & Material Groups	Customers and materials are grouped at master data level	Ability to group customers via Membership lists for customers or Product lists/ Flexible grouping for Materials.
Buying groups or GPO's Note: There are situations when the rebates are to be processed for a buying group who does not actually purchase the products but gets a royalty for introducing customers to manufacturers.	No standard functionality exists.	The invoices can be process separately for buying groups and individual customers. Accural/settlements can be handled accordingly.
Stop Rebate payments	Manual check for Customer AR Clearance.  Cannot stop payments to customers even if customer AR due.	Vistex Payment schedule process handles payments Ability to stop accural if AR not cleared.
Manual Claim process	Standard process part of rebate configuration	Additional configuration to handle manual claims for positive and negative postings
Sales Commissions	Normally clients use the SAP rebates module and generate credit memos for payments	Vistex Payroll profile integrates with HR and payments processed from HR module as part of Payroll
Note: Vistex provides additional modules such as Chargebacks, billbacks, Sales Commissions, Purchasing Rebates and Data Maintenance module (Price optimization tool) that have been implemented by clients for business specific requirements.