cancel
Showing results for 
Search instead for 
Did you mean: 

Order confirmations with several users

Former Member
0 Kudos

Hi

We have a scenario where one or more users will work and confirm the same operation, with the same quantities and at the same time (2 or 3 workers working in the same task) and the system should handle and save those information, because the customer would like to track every confirmations.

Did anybody face the same situation ?

Do you need a new table "Z" to save the users of a confirmation or is there any way to save it without a new table ?

Accepted Solutions (1)

Accepted Solutions (1)

former_member206498
Contributor
0 Kudos

Hi Michel,

It is not possible if you are using standard transaction code, since by the time you enter the production order, the system will raise an error message because of locked object.

You can develop a custom program that allow multiple entries. I ever did the same thing (in my case, the client wanted to have simpler transaction). The confirmations are recorded in a custom table and the program call standard transaction to post the confirmation to the standard tables. For your case, you can create a batch program that frequently post the stored confirmation from custom table to standard tables.

Regards,

Julian

Answers (2)

Answers (2)

Former Member
0 Kudos

ok, thank you Neal, Ramagiri, Julian.

So I will create a "Z" table to save the users that worked in that operation confirmation. The new program should first create the standard confirmation calling the respective bapi and after that, save the users in the new table.

But how can I link the sap standard confirmation with the entries in my "Z" table ?

Former Member
0 Kudos

If I am remembering correctly, the confirmation number is returned in your BAPI.  Take that and use it as part of the key in your new table.  Then it is tracable in both directions.  For instance, you could easily report on via query.

Neal

Former Member
0 Kudos

Another alternative would be to report on it via change history of your confirmation.

Neal

former_member206498
Contributor
0 Kudos

Hi Michel,

As Neal has already mentioned, it is better to link back the confirmation number and counter to each record in your custom table.

You should also think about the way cancellation is done. In standard SAP, if you are cancel a confirmation, you don't delete the record or merely put deletion indicator on the respective record, but you post a cancellation record instead. So, in your custom table, it is better to put two additional fields: cancellation indicator and confirmation number and counter which cancels it.

Regards,

Julian

former_member184666
Active Contributor
0 Kudos

Hi Michel,

As experts already suggested please make note of various check points and ensure the same in your coding.

  1. In AFRU Confirmation number and counter are the key fields. Any confirmation activity done should update the Ztable with respect to this two fileds.
  2. As confirmations are done paraellel by mulltiple users need to have restriction with respective to the order/operation qty.
  3. Cancellation in AFRU will not overwrite instead created seperate record in AFRU and updates the reason for failure text if maintained. It also changes the status in JEST tables.
  4. I believe you will not include auto goods issue with confirmations.

Thanks & Regards,

Ramagiri

Former Member
0 Kudos

Please let us know if you are still having problems...

Neal

Former Member
0 Kudos

Can they wait say 30 sec to issue their confirmations?  It's just a mater of the write process locking while one is entering.  Would that be alright?

Neal

former_member184666
Active Contributor
0 Kudos

Hi Michel,

Customer would like to track all confirmations is good. But when one user is doing confirmation he is giving the reference of order number and operation number. Based on this reference when order/operation is confirmed data updated in AFRU table. At the same time if one more user tries to do the confirmation he also need to refer the same order number and needs to update the same table. If system allows to do such type of confirmation there will be data inconsistancy. Even you want to try out by saving the user 2 confirmation in ztable for him the reference will be order number which system will not allow.

If is not advisable and not possible to do confirmations by multiple users at the same time refering to same order. This is SAP standard restriction to avoid data inconsistancy.

Best way is do configure the system by putting restriction in config for plant and order type in OPK4 confirmation parameters by following error if sequence is not adhered during confirmation and error for over delivery and under delivery. This way every operation will be confirmed in sequence. If operation 0010 is not confirmed then operation 0020 cannot be confirmed.

Regards,

Ramagiri