cancel
Showing results for 
Search instead for 
Did you mean: 

SAP PI - SAP AII Integration: PML File integration issue

former_member216353
Participant
0 Kudos

Hi all,

For a specific requirement, we have designed the interface as below

Interface Requirement - Legacy application will send a huge size PML file.

SAP PI has to split the file and send each splitted chunk to SAP Auto-ID applicaiton.

Legacy Application(PML File) -->(File Adapter)-->SAP PI(AEX)-->(SOAP XI3.0)-->SAP Auto-ID(AII)

We are able to pick the huge file(60-70 MB) and split it in PI.

While the messages are getting posted to SAP Auto-ID, the transactions are getting locked in SAP-AII SLG1 Tcode.

At SAP Auto-ID, ABAP proxy is receiving the message from PI and internally it is invoking a HTTP service in SAP AII engine to update the records.

The error desc in SLG1 says -

Physical object (01)05000456952071(21)1000000000000000xxxx currently is locked by another process

The PML file contains data for a single pallet and the associated Cases and Items and all this data is coming under the <observation> and <tag> segment of the PML file.

Did anyone encounter this issue while integration SAP PI with SAP Auto-ID system .

Is there any way we can get this issue resolved from PI end.

Thanks in advance.

regards,

Younus

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Younus,

QOS will always be determined at the sender. Hence in this case if QoS is EOIO this means, first file is picked up and the next file will be picked up only after the first one is processed in PI. However since the split of one file happens in PI at the Interface determination level. Please confirm if Maintain Order at Runtime Paramter is checked in the Receiver Interfaces tab of your ICO.

Regards,

Sriram

vishal1889
Active Participant
0 Kudos

Hi Younus,

As I understand the problem is happening because the time in which your target system is receiving message is less than the time it is taking to process one message hence the object is found locked by previous message when it is referred by a later one.

I believe using the EOIO option in the file sender channel should fix your problem, as it will keep the later messages in scheduled status until first one is processed.

Regards

VJ

former_member216353
Participant
0 Kudos

Hi Vishal,

Thanks for the inputs.

Yes we have enables EOIO in the file sender. But the issue is still persisting.

As it is a ABAP Proxy at receiver side, do we have any mechanism to enable queueing at SAP Auto-Id system as well.

regards,

Younus