cancel
Showing results for 
Search instead for 
Did you mean: 

constant values to be mapped to fields in control record of InboundIDoc

Former Member
0 Kudos

Hi Experts,

We are currently using PI 7.31 SP11 single stack. Scenario is simple File to IDoc . The message processed successfully in PI but IDoc are with status 56.  In we20 of Receiver R3 system under outbound parameters I could see Receiver port , Partner No. but here since Inbound scenario what values need to hardcoded to the SNDPOR,SNDPRN, SNDRT & RCVPOR, RCVPRN fields in control record field EDI_DC40 ? now I mapped constant 1 to all SNDPOR,SNDPRN, SNDRT but RCVPOR, RCVPRN  as values in Receiver port as shown in first screen shot below. Done settings in we21, bd54. But still IDoc is in status 56 . In we19 when I press Start Inbound then it shows below screen but whereas profile maintained already in we 20 of receiver ECC system.

I maintained only port in we21 with T type destination that contains same program ID & PO host and gateway details. Kindly guide on settings to ber maintained Inbound IDoc configuration scenario.

Thnx,Nithin.



Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Mudassir,


Thanks for reply! No sender port exist so I need to create port in we21 while creating that what type of destination like 3,G,H,T etc should be assigned to that port and  & also the user used in that destination should have have what roles? also what type of destination should be assigned to the receiver port & user roles required in that destination? . To map the constant value to SNDPRN should I create logical system in BD64 and assign the same name? for RCVPRN I will assign the logical system name as constant while mapping.


Thnx,Nithin.

Former Member
0 Kudos

Hello Nithin,

Yes, before creating port create rfc destination in sm59 type T. You will be using Programme ID which will be used in PI (Resource adapter InboundRA).

Regards,

Mudassir

Answers (7)

Answers (7)

Former Member
0 Kudos

Hi All,

Suppose I have imported the DESADV.DELVRY05.ZDESADV which is extended IDoc from R3 system and it is CSV to IDoc scenario. So what constant values to be mapped to  IDOCTYP [XPath:/DELVRY07/IDOC/EDI_DC40/IDOCTYP]  &  MESTYP  [XPath: /DELVRY07/IDOC/EDI_DC40/IDOCTYP] .


Also what constant value needs to be mapped to CIMTYP [/DELVRY07/IDOC/EDI_DC40/CIMTYP] ?

What is IDoc and Message type here?

Thanks,Nithin.

Former Member
0 Kudos

Hi Mudassir,


Pls read all of my questions completely and answer each of them kindly

I thought of re-creating both sender & receiver port again so should I create in ECC only ?  you mean for both of the port creations I have to use two T type destinations or can I use the same one those created in ECC ? if two different T type destinations in ECC for both sender and receiver port then should I create two destinations in NWA of PO?

Thnx,Nithin.

Former Member
0 Kudos

Hi,

Have you worked on PI 7.31 single stack or IDoc_AAE adapter. Pls go through my entire post, it's new ECC system so only one port existing in we21 and should I create port for PI also in we21 of ECC you mean and what parameter indicates is the logical name in we20 ?

Thnx,Nithin.

Former Member
0 Kudos

Nithin,

Go to Tx WE19 , using idoc number in error.Try testing the idoc using value lilst in Sender port (If no sender found then create one) for receiver port use logical system id,for example SAPD10.

If partner profile is configured with the required port then it should work.

Regards,

Former Member
0 Kudos

Hi Mani,

Thank u for reply, can you pls guide on how to create the port and partner in single stack of PI. If there is some prob in PI then the msg should have been failed in PI only right.

Thnx,Nithin.

Former Member
0 Kudos

Hello Mani,

You can create port using Tx WE21 , i believe you have it created looking at your attached Pic.

Make sure you have all these fields are mapped in header.

Try using WE19 to test the inbound idoc with appropriate values before mapping and sending to SAP from PI.

Regards,

Mudassir

Former Member
0 Kudos

Hi Mudassir,

Thank u for reply! Hope u knew that I am using single stack. Where did you create port SAP POD and  SAPPRN as HRACCESS? or what is the source for those values. You mean I have to create ports for both PI & ECC system in WE21 like SAPxxx where xxx is sys ID?  Kindly guide.

Thnx,Nithin.

Former Member
0 Kudos

Hello Nithin,

Check Your Partner profile configuration before creating sender port , whereas receiver port is logical and uses your logical system name. Try testing an inbound idoc in we19 using these values.

I hope it helps.

Regards,

Mudassir

Former Member
0 Kudos

Hello Nitin ,

If your IDoc is failing with status 56 then please check WE57 tcode in ECC to find out whether your idoc type/message type is linked to the function module or not.

Adding the linking might solve your problem.

Thanks.

manigram
Active Participant
0 Kudos

Hello ,

Create the Port, partner in the both the system and pass that values in mapping.

Constantt values 1 in partners fields is wrong, you cannot create the idoc in backend

Regards,

Manigandan

Former Member
0 Kudos

Hi Gaurav,

Thanks for reply! BTW using standard IDoc and msg type & maintained the DESADV and DELVRY03 linked to the function module by two process DELS and DESA in inbound parameters of we20 but no luck again still the new IDocs in 56 status.

Thnx,Nithin.

Former Member
0 Kudos

Hello Nitin ,

have you checked WE57?? In my system i was only able to find DESADV linked to DELVRY05 and not to 03.

Thanks.

Former Member
0 Kudos

Hi Gaurav,

Yes DESADV is linked to DELVRY05 & DELVRY03 also with process code DESA which I have mentioned in WE20 Inbound partner profile also.

Thnx,Nithin.

Former Member
0 Kudos

Hello Nitin ,

As per the WE57 Screenshot the FM name is IDOC_INPUT_DESADV1.

However the partner profile is having IDOC_INPUT_DESADV.

Thanks.

Former Member
0 Kudos

Hi Gaurav,

Earlier I tried with process code DELS linked to module IDOC_INPUT_DESADV only but still I tried again as u said & re-triggered the file but still in 56 status only in ECC.

Thnx,Nithin.

Former Member
0 Kudos

Hi Raghu,

When I enable that "Apply Control Records from Payload" it failed in PI with Recipient Partner Type is not available but when I disabled that it processed in PI but in receiver ECC system with status 56. As said above I mapped SNDPOR, SNDPRN , SNDPRT with constant value "1" whereas the RCVPOR with receiver port value under outbound parameters in we20 and RCVPRN with Partner No. in we20 . Hence, guide me on settings to be made in ECC system especially partner profile part. in we20.

Thnx,Nithin.

former_member186851
Active Contributor
0 Kudos

Nithin,

If your giving control records in the Mapping,make sure "control records from payload" option is selected in the receiver IDOC channel