Split Payment - PL_ELIXIR-O new version

[former_member671099]

Hi Team,

I am implementing Split Payment settings for Poland in according to SAP Note 2624533 and 2168056 SAP advices to upload a new version of PL_ELIXIR-O file. They as well attach the file but only in xml extension while our bank requires pli or ple extension.

Has someone worked with pli or ple file? How can I get a new updated version of this file to upload to DMEE Tree?

Regards,

[MarekTurczynski]

Hi Marta,

the attached XML file is just the structure of DMEE which you can upload via DMEE transaction using menu option Format Tree - Ulopad XML File.

After loading you will see that it is the flat file (you can see the same in the XML file attached to OSS notes mentioned in field XMLTree - it is empty so it means it is a flat file).

SAP does not support Elixir format in XML format (there is no country-specific tree in XML format for PL) - it only delivers flat fliles which are exactly the PLI/E files.

Regards,

Marek

[former_member671099]

Thank you Marek for your support:)

Regards,

[Private_Member_602983]

Hi,

Can you please share the step by step procedure on how to implement VAT Split and how to validate/test it after implementation.

Thank you in advance.

Regards,

SG

[former_member671099]

Hi Marek,

The error message pops up when I try to activate/ click on DMEE tree check in left upper corner. The error message says: "Error in conditions node for Payer BBAN/IBAN: source field FPM_PL_ELIXIR-PL_IBAN/

source field FPM_PL_ELIXIR-PL_BBAN does not exist.

I have just found one of collective SAP notes 2168056 -

Collective note for payment formats: PL_ELIXIR-O - I am talking about the note number: 2888854 - PL_ELIXIR-O: Bank number in IBAN and BBAN format.

From what I see reading this note it should resolve my issue.

I have a question - we have not proceeded with implementation of SAP Notes included in collective note 2168058 yet. The note 2888854 is one of these notes.

Would you recommend to implement all the sap notes mentioned in

2168058

?

Thank you once again for your support

Marta:)

[MarekTurczynski]

Please follow the steps from the OSS notes - so first implement the OSS note (and all its dependencies - among which the note

2888854 will be available). To solve your activation error please just implement the note 2888854.

Marek

[former_member671099]

when I uploaded the file the system displayed message - PL_ELIXIR-O already exists.

I bypassed the message and saved then tried to activate the tree and the system displayed error message:

Format tree PL_ELIXIR-O inconsistent (see log); tree saved in maintenance version

Message no. DMEE_ABA203

I do not know how to proceed.

[MarekTurczynski]

What does to log say? In which node the error is existing?

Did you implement the OSS notes for Split Payment?

[former_member671099]

Good morning Marek,

Thank you a lot.

Last question - is this transportable change or should I separately upload the xml into each single environment?

With kind regards,

[MarekTurczynski]

Change is transportable - when you upload the file then system will display you the DMEE content (structure ) and after clicking on activation button system will prompt for transprot request (workbench).

[former_member671099]

Thank you once again Marek,

I am having another issue: in the note

2624533 and one of collective notes of 2168056 I found examples of PL_ELIXIR-O xml to be uploaded but for Basis Release 700 and 750 while our sap_basis component is 731. Should I choose lower version for Basis Release 700?

My last question - we have already electronic payment payment type - does split payment require a separate payment type to be created in FBZP?

Thank you in advance Marek:)

[MarekTurczynski]

In regards to DMEE Treee the basis component will not hinder you from uplaod. Please upload the file normally via the upload function. The coding itself for the functionality is included in function module FI_PAYMEDIUM_DMEE_PL_ELIXIR_05 which is delivered by the OSS notes mentioned by you.

The required customizing is to create a new payment method solely for Split Payment and enter it in view V_IDPL_PM.

The field FPAYH-REF05 will return the concatenated payment description valid for split payment.

[former_member671099]

Marek,

thank you a lot for your reply.

I have noticed that I just should proceed following SAP instructions and that there is no physical file to be loaded.

I tried to copy existing version before loading the new one but when trying to copy source format tree - maintenance version the system displays warning that "format tree does not exist". Should I then copy "active version"?

[MarekTurczynski]

Yes, if active version exists it is best to copy that one (this is the one which was activated as last) - so this is the last usable version. Copy that one first as backup and then upload the new one.