Enqueue Read Validation

[jagan_krishnan8571]

Hi,

We are having a Z table containing credit limit wrt customer, business, payment terms and an Unique Id. Whenever this Unique Id is attached to any sale order @ Sales order creation or Sales order change, the payment terms gets attached with the order.

Also, the credit limit gets consumed accordingly wrt current order value and the orders in which this Unique Id is attached. For correct credit limit consumption, we have enabled lock/Enqueue for the orders wrt Unique Id(thats like, users cannot simultaneously save multiple orders with same Unique Id, it happens one by one)

Question:

1. Business says, we are unable to process orders simultaneously, they want users to save orders without enqueue, still want correct credit limit consumption - Is there anyway out for this?

2. Can we do like this - While doing Enqueue while creating or changing order containing Unique Id, can we pass capping credit limits for each simultaneous order save in SM12 and read the same in "USEREXIT_SAVE_DOCUMENT" and use below code to stop further processing of order -- Will there be a sales order number skip as SO number would get generated in this exit?

MESSAGE Sxxx. "to tell the user what's the problem
PERFORM FOLGE_GLEICHSETZEN(SAPLV00F).
FCODE = 'ENT1'.
SET SCREEN SYST-DYNNR.
LEAVE SCREEN.

While we do understand, validations have to happen in USEREXIT_SAVE_DOCUMENT_PREPARE, but we are not getting the exact SO value in USEREXIT_SAVE_DOCUMENT_PREPARE, as freight and tax computation happens only in "USEREXIT_CHECK_VBAK" or in "USEREXIT_CHECK_VBAP".

Waiting for your suggestions

With Regards,
Jagan

[jagan_krishnan8571]

Guys, can anybody help on this

[RaymondGiuseppi]

Can you elaborate on "as freight and tax computation happens only in "USEREXIT_CHECK_VBAK" or in "USEREXIT_CHECK_VBAP". this shouldn't be the case, did you execute an Abap Trace to check (SAT) or debug to insure those changes occur after the userexit_save_document_prepare ?

[jagan_krishnan8571]

Hi Raymond,

Thanks for taking your time to respond.

Because of company policy, i am unable to share screen shots for this.

Its like, when we are creating a sales order, via VA01, the base amount which we provide at line item level in condition tab (say $7000) is only we are getting as SO net value, when system reaches "USEREXIT_SAVE_DOCUMENT_PREPARE" --> MV45AFZZ, but when system reaches "USEREXIT_CHECK_VBAK" or "USEREXIT_CHECK_VBAP" --> MV45AFZB, total order value changes to (order value + freight value)--> 7000 + 250 (say) put together shows $7250 and this is what is getting saved into VBAK and on order display via VA03.

Can you please throw some light on below point plz --> This is what is completely conflicting between IT and Business Team in here:

Business says, we are unable to process orders simultaneously, they want users to save orders without enqueue, still want correct credit limit consumption - Is there anyway out for this? [Users use SAP GUI to create sales orders]

With Regards,

Jagan

[RaymondGiuseppi · Accepted solution]

Strange, as SAP also does its check in the main form beleg_sichern, something seems wrong in your current user-exits there, some forms intended for check are used for update, you should correct this first, use forms like USEREXIT_MOVE_FIELD or PREPARE instead of CHECK.

Only lock the credit record in USEREXIT_SAVE_DOCUMENT_PREPARE, last statements suggested, if already locked, stop saving with gf_exit_save_document_prepare = 'X' and a message 'sorry locked, please try again', if not locked and not enough credit, unlock, send a message 'no more credit' and stop saving in the same way. Otherwise, register the credit limit update in any FM update task. The commit will release the record.

In USEREXIT_SAVE_DOCUMENT it's too late, you can only abort the transaction in case of failure, so user input is lost.

SAP also provides such a credit limit in the standard, was not accepted?

[jagan_krishnan8571 · Accepted solution]

Thanks for your response Raymond, this helped.