Skip to main content

Requirement to restrict business user from releasing sales document more than once after credit block

Business Requirement:

If the customer is blocked due to credit then credit release should happen only for the first time.
When the second order is created for the customer and is blocked for credit then the system should through error message with below info

Solution approach:

Userexit_SAVE_DOCUMENT

Logic

If SY-TCODE EQ ‘VKM4’

Pass KUNNR into Table VBAK and fetch all entries where VBAK – CMGST = ‘D’ and VBAK-GBSTK and VBAK-LFSTK = ‘C’

If SY-SUBRC is INITIAL
Pass VBELN into table VBFA-VBELV and fetch VBELN with VBTYP_N = ‘M’

If SY-SUBRC is INITIAL
Pass VBELN into Table BSID – ZUONR and fetch BELNR

If SY-SUBRC is INITIAL

Message ‘Payment pending for Order exist. Hence cannot release this Sales Order’ type ‘E’.

Comments

  1. I really like your blog.. very nice colors & theme. Did you design this website yourself or did you hire someone to do it for you? Plz answer back as I'm looking to create my own blog and would like to know where u got this from. thank you. reefer for sale

    ReplyDelete

Post a Comment

Popular posts from this blog

[SAP EWM] Batch job to reprocess the failed queues in SMQ1 and SMQ2

Reports RSQOWKEX/RSQIWKEX can be scheduled as a periodic background job to reset the status of LUWs registered to outbound(SMQ1)/inbound(SMQ2) queues. RSQOWKEX for outbound queues (SMQS/SMQ1). RSQIWKEX for inbound queues (SMQR/SMQ2). The below parameters are to be maintained : Queue Name as '*' Select 'No Running Queues' Do not select 'No Retry queus' Queues running longer than  < Time in Mins > ideally 20 mins No queues older than < Data > Note that this job will change the status of the failed queue to 'READY' status so that scheduler will process it. But for any queues struck in 'READY' status, th ese need to be processed manually.

[SAP SD] Mass deletion of deliveries in SAP

If there is the requirement for collective deletion of Outbound deliveries in standard, the following can be performed. Transaction VL10* with corresponding user role settings can meet this requirement. Go to VL10*, only flag indicator 'With Deliveries' in 'Data Selection' column in User Role After flagging above indicator, go into the following screen. Then flag indicator of 'Add to delivery', and fill the delivery numbers or other parameters into corresponding fields and then execute In the display screen, select the lines and click 'Delete' button

How to change records in SAP using debug mode

This post explains how database update can be performed through transaction codes SE16N and SE16. At times, there might be a situation in the test environment where we are required to perform database updates in order to manipulate or try to replicate a case in a lower environment. Database contents in SAP can be viewed through transaction codes SE16N or SE16. This post explains how the database update can be performed for both transaction codes through debug mode. Case 1: Transaction Code SE16 In this case, I have taken a sample example to update the VBAK table entry through debug mode. Enter Sales Order Number Select the entry displayed enter '/H' in the command bar and click on ok or enter button. Then click on entering again after debugging activation to enter into debugging screen Click on the 'Code' then display as 'SHOW' on the right side of the screen. Then we will change it to 'EDIT' as we are trying to change th...