ALE: FI-IDoc FIDCCP01/FIDCCP02

Question

Hi all,
i have a problem with creating and sending IDocs for FI-Documents. I use Message type FIDCC1 and the IDoc Basictype FIDCCP01 (with an extension). In the Partnerprofiles i maintained this data combination. But by posting an FI Document an IDoc with IDoc type FIDCCP02 is created but faulty with the reason of not existing entries in the outbound table. The reason of faulty is correct, but i do not really understand why an FIDCCP02 is created. I assume that the reason is the used function module 'FI_IDOC_CREATE_FIDCC1' (i think that is used) and the IDoc type that is used is hard coded FIDCCP02. But some created IDocs fit to my maintained partner profile (FIDCCP01 with extension). So that i am really confused and do not really know what has to be done now.
An OSS message (459938) says that the old FIDCCP01 still can be used. How?
I am working with a 46B (PatchLevel 51).
Please help.
Thanks in advance
Michael

Answer 1

Hi,
in WE20 you maintain the partner profile. Selecting a partner you see which messages are distributed (outbound and inbound). If you select a message type and show the details (for example Screen 'Partner profiles: Outbound parameters) you see in addition to the message type a field for message code (3 digits) and message function (3 digits). With these two additional informations you can separate processes using the same message type.
Think about several systems sending data with one message type to one central system and you want to handle the inbound different. Therefore you can use message codes and message functions.
My problem was that i didn't really know what i did when i used this the first time. We wanted to distribute the message FIDCC1 with the IDoc type FIDCCP01. We have done several times with other systems and it always runs without any problems. But when i started using MESCOD and/or MESFCT an error appears with IDoc type FIDCCP02 and that our additional segment is not identifyable).
So i had a look how the ALE service version conversion works. As i wrote before our Application creates a master IDoc with type FIDCCP02 and former this was converted to FIDCCP01.
It is done like following (sequences of calls):
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
PERFORM 'IDOC_SELECTION_AND_SERVICES'
CALL FUNCTION 'ALE_IDOC_SERVICES_APPLY_OUT'
PERFORM 'IDOC_CONVERT_VERSION_OUTBOUND'
PERFORM 'CHANGE_IDOC_VERSION'
The program takes the values of the IDoc control information (MSGTYP, MESCOD, MESFCT) and checks them against table EDP13. If an entry exists the change of the IDoc version will be done, else not.
So my fault was to maintain the partner profile with MESCOD and MESFCT but in the control information these values were empty (how should the application program know which walue have to be filled in?). So i did it in an exit (F050S004 FM EXIT_SAPLF050_007):
>>> Enrich IDoc Control structure with a value for the logical
    message function, to make a difference for different processes in
    the partner profile.
  idoc_control-mesfct = c_mesfct_fidcc1.  "YFA
Now it fits to my partner profile and it runs properly.
But don't forget to maintain the partner profile in the receiving system equal and VERY IMPORTANT think about the inbound processing. You have to maintain the Assignment of the inbound FM to log. Message and IDoc type with MESCOD and MESFCT using transaction WE57.
Thats all.
Hope it helps.
Michael