Skip to main content

Status Profile - Sales Documents

This concept is similar to release strategy concept at purchasing level. At times, the business user requires approval to proceed with the next activity of the sales process upon approval from senior executive or manager. This approval process can be set up to status profile concept.

The status profile can be used in the various component such as Sales, QM, PP etc. In the below case, We will discuss the application of the status profile in sales and distribution module at sales document type level.

This is ideally used during complaints processing such as returns, Credit Memo Request etc..

In Sales documents, we can maintain the status profile at Sales document header and Item level.

Here we will discuss regarding the maintenance of the sales document at Header level.

Below is the config setting need to be maintained :

Goto T.Code BS02 and click on create



Based on the approval levels maintain the statuses. In the below instance I have taken two levels of approval to create a subsequent document for sales order creation.

Goto BS52, Create authorization code and assign against the respective status line item.


Click on object types to view the different levels at which status profile can be applied.




Select 'Sales Order header' for header level check.


Then go back to the item screen and select line item and click on details to control the subsequent document creation.


In this case, we have restricted order with the initial status as forbidden, so that subsequent documents will not be restricted from creation.



For the final approval status, we will select the allowed for creation so that subsequent document will be created.

Upon creation of the status profile,   Maintain status management for authorization object B_USERSTAT, specify object category as chosen (VBK (Header)or VBP ( Item), authorization key, and status profile. Generate authorization.

Assign status profile to required sales document type.



Business Process

Create Sales Order with Order type ' OR'.







Comments

  1. Nice information on here, I would like to share with you all my experience trying to get a loan to expand my Clothing Business here in Malaysia. It was really hard on my business going down due to my little short time illness then when I got heal I needed a fund to set it up again for me to begin so I came across Mr Benjamin a loan consultant officer at Le_Meridian Funding Service He asked me of my business project and I told him i already owned One and i just needed loan of 200,000.00 USD he gave me form to fill and I did also he asked me of my Valid ID in few days They did the transfer and my loan was granted. I really want to appreciate there effort also try to get this to anyone looking for business loan or other financial issues to Contact Le_Meridian Funding Service On Email: lfdsloans@lemeridianfds.com / lfdsloans@outlook.com He also available on WhatsApp Contact:+1-9893943740.

    ReplyDelete

Post a Comment

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...