Error in IDOC load for BBP_PCSTAT Partner Profiles

HI,
We use BBP_PCSTAT to load p-card transactions in to SRM on an inbound IDOC. This has worked fine for two years & now suddenly we are getting problems!!
the first record in the interface file loads fine - the idoc succeeds with a status of 53. Each subsequent idoc fails with status of 51 and the following error:
No partner profile (outbound parameter) could be found using the following key:
/0000000000/LS//////
This refers to the key fields in table EDP13:
RCVPRN Partner number
RCVPRT Partner type
RCVPFC Partner function
MESTYP Logical message
MESTYP Message code
MESCOD Message function
TEST Test indicator
Procedure
Please check the EDI partner profiles.
Has anyone seen this before?? we are a bit stuck now!!!!
Many Thanks

Hi yes, as far as i can see our SRP and ERP systems are in existance in WE20 under logical systems.
We are using a bespoke program to load these through, as part of the parameter process we have a variant the defines the sender and receiver systems. This variant has not changed & nor has the We20 entries as far as we can see..
We ran the process one month ago and everythign was fine.
I dont suppose you are the same Keith Wood worked on the project here at the isle of wight are you?!

Similar Messages

TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and

Hi All
Can anyone pls give me all the TC related for IDOC (Defining Port,Defining Partner Profiles...etc) RFC and BAPI
Thanks
ss

Hi SS..
 SM59-For creating the RFC destination
 we21- For ports
 we20-Partner profiles.
For more inforamtion Please look at the below information:
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP XI towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
 Thanks and Regards,
 Chandu.
Message was edited by:
 Chandu
null

Using SYPART01 IDOC for setting partner profiles from external system

We wish to maintain our partner profiles from an external system.
Is there any existing interface for doing this.
It seems that the sypart message is only for output, not input.
Any ideas or suggestions?
Thanks!
Dan

Hello Dan,
Thanks for your post.
I hope the following code helps in future.
http://wiki.sdn.sap.com/wiki/display/Snippets/Copy+partner+profiles+with+SYPART+message+quickly.

IDOC status 30 but partner profile is set to send immediately (04)

Hi guys,
I have a problem with idocs not being sent immediately... The outputs, the EDI partner profiles are all set up correctly...
it is configured to send immediately however, it's not doing so... prior to upgrade to ECC 6.0 it's working fine... now its not...
However, in BD87 thru manual release of IDocs, it is working fine...
Is there any changes to ECC 6.0 for this matter? or is there anything that needs to be set up other than those mentioned above in order for it to work in ECC 6.0?
Thanks a lot!

Mark, have you looked at the OSS notes? By 'IDOC status 30' it finds 300+ notes, this is really a wide-spread issue.
The most recent one is 150202, which actually recommends collecting the IDocs instead of having "send immediately" because it saves the RFC resources. This is not really an ABAP issue, so you might want to discuss this with your Basis admin.
Also, from my experience, even with "mission critical" processes the users, in fact, never feel any real difference between "immediate" and 5-10 min. Sometimes (due to a technical problem, for example) nothing goes on for 30+ min. and no one even notices.

Receiving IDoc SYPART01 (Transfer of partner profiles)

Hi, well this is not a special PI issue but we have the problem to receive the SYPART01-Idoc in target system.
This is due to not knowing the process code for inbound processing in target system. We already used BAPI, searched for Function Modules etc. - but with no success.
How do you guys transport partner profiles from one client or system to another?!
Or does someone know how to manage the inbound processing for IDoc SYPART01 ?!
br Fritz

Hello,
Any news on this subject ? I'm interested by this topic.
I noticed there must be some specific FM in Emmanuel Hadzipetros SAP Press book.
I guess there aren't any "standard" way !?
I tried to figure out something and notice in the SED package that there are RFC FM like EDI_AGREE_PARTNER_INSERT, maybe we could find out a LSMW solution.
Jon

Error in IDOC ststus , for interface IDOC to File

Hi All,
iI am doing IDOC to file interface , in which i am using IDOC Orders05, we are using the same IDOC for other interface to connect with DOTNET connectors , when i trigger the IDOC ORDERS05 for my interface when i check the ststus , in which it is pointing the to partner No and Port to that dontnet, not to my Iterface for SAP XI , anyone there to help me in this isssue
Thanking you
Sridhar

Hello,
While sending Idoc you will be providing the Port which in turn needs RFC Destination and this is one which takes the document to External system configured in RFC.
If you need to send the idoc to External Systems other than R/3 then you need to use T type connection which uses JCO for estblishing session. if it is R/3 then requires logon credentails and type 3 for configuring RFC.
HTH
Rajesh

Error "No INBOX Selection for the Partner".

Hi Experts,
Could someone please tell me where we can configure a Vendor for "No INBOX Selection for the Partner".
Is this at some transaction level or in the Shopping cart.
We have this field in the table CRMD_PARTNER, Field - DISABLED
Due to this the Vendor gets dropped and the PO goes into HELD status.
We have implemented the Preferred to FIxed Vendor and works perfectly, except for these partners with CRMD_PARTNER-DISABLED = 'X'.
Thank you.

thanks

Error in IDOC CREMAS for Bank data

Hi,
I am trying to upload vendor master through IDOC.I am also sending bank data in my IDOC.But it gives the below error
Fill all required fields SAPLBANK 0100 BNKA-BANKA
We have created the bank and details exist for that bank.
We are giving Bank Country Key,BANKKEY and BANKACCOUNTNUMBER details in IDOC.
When I have Reprocessed the IDOC thru WE19 in Foreground mode It goes to bank screen twice.First time the okcode is 06 and second time the okcode is 16 which take the control to other screen where it ask bank name.But Bank name already exist for that bank.we are not giving bankname from the idoc.
Any help appericiated.
Thanx.
Rekha.

Sidenote because this thread is one of the first results in google when searching for "SAPLBANK 0100 BNKA-BANKA":
Please have a look at [SAP OSS Note : 697492 ALE: Bank master data updated - DEBMAS|http://www.google.de/url?sa=t&rct=j&q=sap%20oss%20note%20%3A%20697492%20ale%3A%20bank%20master%20data%20updated%20-%20debmas%20&source=web&cd=1&ved=0CB4QFjAA&url=http%3A%2F%2Fforums.sdn.sap.com%/community [original link is broken]%3FthreadID%3D2047770&ei=PDbWTv6OK4eJhQeY2tlZ&usg=AFQjCNGnp_ieUhM9jNZi9Rd-s-N9i1FNpw&sig2=pmD56XZs_GAtNI3zMsJPLw&cad=rja]
Regards
Martin

Error during delta load for bulk upload data object

Hi All,
I am getting the following message in the backend integration logs for one of the bulk enabled data object.
Error message:
Unable to find parent record for record of node 'CHILD2'.
Message : SMMWKGN class 005.
Does anyone know about this error.
I have defined the the fields as key in child nodes which are defined as key fields in Header structure?
Also while executing the getlist and getdetail i am able to see all the related data?
Can somebody suggest?
Thanks
Dev

found out the problem. Solved

Partner Profile for IDOC - configuration

Hi..
I have an inbound IDOC TPSSHT01, which has been extended by adding a Z segment.. But I keep getting an error message.. The IDOC is created with status 56 and the message says "No inbound profile found".. I have configured the Inbound profile to include the message type 'SHIP' in WE20 and also added the message type in WE57 and WE82... Do i need to do any further settings?
Thanks
Rishi

hI,
Please use transaction code WE20 to generate inbound partner profile
Goto WE20 transaction of the client 200 where you are posting the idoc and maintain the partner profile for the inbound type for the idoc type and the corresponding message type of SHIP. This is because you would have maintained it as the outbound parameter from client 100. But at the receiver end also you need to configure the same.
Status 56 comes up when the partner profile for the idoc type is not maintained. Once its maintained, the idocs which you post will go into 53 if its successfully processed and to 51 if its failing due to any inbound processing program validation
*Reward points
Regards

Generating partner profile for File to Idoc(CREMAS) scenario.

Dear friend,
Completed all the steps in SLD, IR and ID.
I do not know how to create Partner profile and I skipped this step.
While testing I got the error "Unable to convert sender service to an ALE logical system".
I think i got this error because I have not created partner profile.
Could anybody tell step by step process of creating partner profile including logical system names( Sender and Receiver)?
I have seen many blogs and i couldn't get clear picture on how to generate partner profile.
My sender system is XI server and receiver is R/3.
I have created RFC destination, Port also.
Thanks in Advance
Chiru

generally u create partner profiles using transaction WE20.
SAP Menu -> Tools -> IDoc Interface/ALE -> Administration -> Runtime Settings -> Partner Agreement (WE20).
go through this link for step by steps
http://help.sap.com/saphelp_nw2004s/helpdata/en/dc/6b808e43d711d1893e0000e8323c4f/content.htm
http://www.thespot4sap.com/Articles/SAP_ALE_Configuring.asp

EDI: Partner profile Error

Dear All,
I was trying to load a Hierarchy from R/3 to BI 7.0 . I get an error "EDI: Partner profile not available". When I go to R/3 TC we05 I get under Inbound Docs> RSRQST > status 64 for Idocs specifying this error. I donot find RSRQT partner profile under outbound Docs.
When I go to BI TC we05 I get Inbound Docs empty and Outbound docs > RSRQT I donot find the above Idoc numbers having status 64.
What does this mean?How can I successfully load this hierarchy?
Regards,
Jack Silverz

Hi Jack,
Make sure that logical system name hasn't been changed .
Check SAP note 325470.
Hope this helps u...
Regards,
KK.

Partner profile value for XI system

I got a outbound message with partner profile value as
<SAP:SNDPOR>XIDEV</SAP:SNDPOR>
<SAP:SNDPRN>XiALE01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
Where do I go and change the SNDPRN value in SLD? or is it SLD I change it. SAP R3 is looking for sender partner profile in caps. How to change this value in XI
thanks

Hi,
Please update few things.
1. Since it is an outbound from XI into another R/3 machine, I would first suggest you to check IDOC posted in R/3 which has an error message tagged to it. This is applicable only when Message went from XI into R/3 and we see an error in the SXMB_MONI as RFC destination not found etc.,.
In such a case, IDOC error message with 53/51 etc, will post an error message like "SENDER NOT IDENTIFIED". This SENDER and RECEIVERs can be seen in the CONTROL RECORD of the IDOC.
From R/3, use transaction WE02/WE05 and locate your IDOC (normally in the OUTBOUND folder on left, look at last few messages which have RED TRAFFIC SIGNAL and match the partners).
To resolve this, create the RFC PORT first. XIDEV using WE21 referring to your XI client. The prerequisite for this is to have a RFC destination already created to port XI and a logical system (BD54 transaction).
Create a Logical System (Business Partner) of type LS using WE20 and (Logical system you have created or identified in BD54) should be configured as you want.
This should resolve your issue.
2. If the issue is with XI and message is not seen in R/3, make sure you have assigned proper logical system in the SLD for your technical landscape. If this is pointing to a different logical system, then probaboy you may want to change to suitable logical system.
Suggest you to look for the definitions using SM59 and IDX1 in R/3.
Hope this answers, please let us know your findings.
Thanks,
Srini.

IDocs, INVOIC partner profile configuration

Hi,
I need to receive the INVOIC IDocs from sender system.
Sender(S) system is new system
receiver(R) system is already exisitng system.
I tried to configure the inbound settings in receiver syste. But message type INVOIC, process code INVL, FM all are already available and configured for some ohter systems.
Now if i configure only partner profiles and distribution model, then is it work.
Thanks
Kiran

Kiran,
INOVOIC, INVL, Process codes etc come with the standard system. They can be configured for any partner profile and any sender system.
First, you need to determine the inbound connection. Will the new sender system (S) going to follow the same RFC connection already setup for other sender systems? E.g. Are all the inbound IDOC's flowing through PI or a single EAI system?
If yes, then you just need to setup a new partner profile and use the same port already setup for your existing connections.
If no, then you have to determine how the sender system will connect with SAP. Will they drop files in the SAP's application server? After dropping can they execute the startrfc.exe with required parameters. If they can then you can just proceed with creation of a port to listen that folder (assuming the RFC connection is already setup for that connection) and move ahead with partner profile creation and other mandatory setups. If they cannot trigger the startrfc.exe, then you have to define a new RFC destination (SM59) and a new port (WE21) to read data for this RFC destination. You have to determine when to read the data (e.g. explicit host type etc).

IDOC question on Message type and Basic Type - Partner Profile

Hi all,
I am wonder if I can post any IDoc question in this right forum/module. If not please direct me to the right forum/module. I am a newbie in IDOC setup.
My question is about the setup of Partner Profile creation (WE20).
When creating a new partner, for example with partner type LI, I notice there is outbound parameter and inbound parameter.
Questions:
1 u2013 It makes sense to have only one message type record appear in EITHER one of these two tables. I notice that some partner in my system has message type record exist on both the inbound and outbound parameters table, why system allows? What is the business rational?
2 u2013 May I have a list of standard SAPu2019s Message Type object of its usage description, and its allowable Basic Type (ie. IDOC TYPE). Basically a website to describe their (i.e. Message type and its Basic Type) business usage.
Thanks.
tuff

Tuff,
Below are my thoughts,
There is a partner sing partner type LI. This partner in the WE20, has one record (i.e. with Message Type ORDERS) exist in the Outbound Parameter table. This partner also has 4 records (i.w. with Message Type DESADV, INVOIC, MBGMCR, and ORDRSP) exist in the Inbound Parameter table. So my question is what is the business rational behind this kind of setup. Because I am confuse when come to create a partner profile, whether I need to create a message type in Inbound Parameter table or Outbound Parameter table, or I need both.
OK, so looking at the above example, you have an orders message type(This is for creating an order) in the outbound, this means that you are sending out an IDOC(purchase order for ex) to this partner, so that this partner can create an SO in his system and fulfill your order.
Now you also, mention that you have other four Message types for the same partner on the inbound, now let us look at the above scenario, you have asked your partner to fulfill the order, i guess you would like to get a confirmation from him/her if the order was created or not in his/her system and how and when is he/she going to fulfill your order requirement. This he/she does by sending an response to your order - ORDRSP.
And when the partner is ready to ship your order to you, he/she sends out a Advance Shipping Notice - ASN via the IDOC of message type DESADV.
Finally and most importantly , he/she will send you the invoice - INVOIC for the order.
In general, you interact with your partner via Business Docs - Order, Delivery, ASN, Invoice etc, so whatever document come from your partner - ORDRSP, INVOIC etc will be on the inbound profile of the partner. Whatever docs that you send ORDERS, ORDCHG etc etc will be on the outbound profile of the partner.
2 - Bascially I would like a reference in any website that allow me to choose which message type is best use for my partner profile, so that I don't have to reinvent.
Well, there is no choice of choosing/best message type for a given requirement - So for sending an Invoice the message type is INVOIC, ORDERS - For order creation, ORDCHG for order change etc. However the IDOC type, is some thing that you can choose, for Ex: ORDERS01 - ORDERS05, these are the IDOC types that are available, so if you are interacting with a partner who are running an old version of SAP and their system has only upto ORDERS02 in their version of SAP then you would use ORDERS02.
Regards,
Chen

Error in IDOC load for BBP_PCSTAT Partner Profiles

Similar Messages

Maybe you are looking for