Processing duplicate trans from same POSLOG to SAP POSDM.

[former_member461886]

Dear Experts,

I have a scenario where due to some bug at POS system at store it is duplicating one transaction with same transaction number ie. Trans 1234 with sales value $100 is duplicating with same transaction and creating Sales POSLOG XML and pushed to my POSDM through SAP PI, so 2 transactions with same trans # are in single POSLOG XML

Once PI trying to push those trans with BAPI program, they are skipping in middle and not showing up in my TIBQ table, neither it shows POSLOG error in SAP PI also,whatever trans in that POSLOG are not posting to POSDM, so we are clueless until a sales comparison report generates and show variance.

However if those 2 above trans are two different POSLOG XML, they are posting to POSDM and it will fail at Duplicate check.

Any solution we can post those 2 trans to POSDM and get failed with duplicate check.

[vikrant_mohite]

Hi,

If you are having two transactions in single POSLog with same transaction number from same POS Machine and if your PI is able to create the two transactions for POSDM BAPI, POS DM will definitely create two transactions.

I would suggest work with your PI guy and look at what they are passing once the PI mapping transforms XML in required structure and before it calls BAPI for POS DM.

I suspect PI must be treating the transaction number as key and dropping another one.

To start with take POSLog with two transactions of same number and see what is available in PI (Payload post mapping ) before they call BAPI for POS DM in your non prod environment.

Additionally you can avoid those being marked as duplicate in POS DM by adding start timestamp of transaction as key to check duplicate(in POSDM).

Thanks,

Vikrant.

[former_member461886]

Hi Vikrant,

We try to debug the BAPI program, bcz SAP PI successfully pushed the file to BAPI and when I debug the BAPI (/POSDW/BAPI_POSTR_CREATE) it shows the below error "More than one instance of segment FinancialMovement with key 1 for transaction 1627 05.03.2019 9 1302 34805_1"

ie is this getting skipped at BAPI in POSDM ?

any way we can control this and push to TIBQ/POSDM.

[vikrant_mohite]

Thanks for sharing the error.

That looks genuine error because of the way BAPI accepts the transactions. I was under impression you are using RFC call from PI. Even if you use IDoc it will give same result (I think).

Are you getting two transactions combined in one ?

As a solution to have both transaction in POS Workbench I will suggest to append your transaction number with _<Position no of transaction in XML> with the help of PI.

e.g. if you have transaction in following sequence 123, 124, 124, 125 in XML they should be sent to POS DM as 123_1, 124_2, 124_3 and 125_4 from PI.

Implement BAdi for /POSDW/BAPIINPUT_PST where you will remove the extra added things from transaction i.e. search for _ in transaction number and remove anything after it inclusive _.

This way you can get both the transaction in POS Workbench with original transaction number.

I hope this helps 😉 and yes your original transaction number length shouldn't be greater than 16 and incoming XML to PI shouldn't have more than 999 transactions in it.

Thanks,

Vikrant.