Duplicate specification creation

[#1]

Hi All ,

We have a client who sends data via Oasis/PI middleware to SAP EHS system . From client we receive data as XML format to OASIS and then from OASIS Idocs are triggered to SAP EHS system .

When an Idoc is triggered from Oasis to EHS system , it must perform 2 action either creation of specification or updation of specification .

An incoming idoc will check for an entry in ESTRI using design code and then from ESTRH table specification details will be retrieved . If there is no specification available for that design code a new specification will be created or else existing specification will be updated with idoc information .

Also many check and lock mechanism are also implemented to avoid duplicate specification .

Issue :

When two or more idocs triggered at same time its getting proccessed at same time therefore when two idocs search in table there will be no specification available , therefore both idocs creates new specification .

We cannot stop the data getting triggered from client and the only possible way is to implement in EHS system.

Kindly provide me some information to overcome this issue .

regards ,

suresh .

[former_member637181]

Hi All,

We found the root cause for this duplicate specification issue.

Normally when an idoc triggered from PI to EHS system. Idoc will proccess with corresponding status such as 50-->62-->64-->53

There is background job running behind in our SAP system to proccess all the idocs in 64 status.

When the job is exceuted, two or more number of idocs is getting proccessed in same time span and results in duplicate specification creation.

So to avoid this we removed our Partner from the background job which is proccessing the idocs with 64 status.

Thanks everyone Guys !!!!

Regards,

Suresh

[satya11719]

Hello vasanthabalan77

Further add on to the above...

We had similar situation in previous client and we made some fraction of seconds between one idoc to another idoc, So that system will create one spec and other idoc will update the specification. This is the only feasible way we found.

serialization concept in SAP or delay in middle ware will work.

I hope this helps...

Regards

Satya

[christoph_bergemann]

Hello

your topic is not discussed very often and it is a "very special" one. May be you will find ca at max 5 threads

Regarding your last topic: you must check in SAP ERP (EHS System) and try to manage there the process (refer to the hint of Mark)

The "middleware" is not the right place

C.B:

PS: check e.g. https://answers.sap.com/questions/12327599/inbound-submas-idoc-from-external-system.html

is one of the best references which i found on short notice

https://answers.sap.com/questions/12717343/import-long-text-via-idoc-submas02-into-e1bp1077ri.html may be could be of interest as well

https://answers.sap.com/questions/9087412/idoc-from-ehs-tables.html => this is more for "outbound"

[Mark-Pfister]

Hi Suresh,

You need to serialize your IDOC processing:

https://help.sap.com/saphelp_ewm70/helpdata/en/7f/a1ce5314894208e10000000a174cb4/frameset.htm

Best

Mark

[former_member637181]

Hi Mark ,

Thanks for your inputs .

* Do you want us to implement this serialization concept in Middleware or else in EHS system .

Kindly provide us inputs to make changes in EHS system to overcome this issue .

Regards,

Suresh.

[Mark-Pfister]

vasanthabalan77

Only if the IDOCs reach the SAP System in the right order and SAP processes them in the right order (serialized) it will work....

[holger_hartung]

Hi,

you could manage the Idoc processing step by step with report

RBDAPP01

[former_member637181]

Hi Holger ,

Thanks for your inputs , but still we receive huge amount of idocs and we cant process every idoc individually.

Kidnly provide me any other inputs to overcome this issue .

Regards ,

Suresh