Process code & Partner Profile Issue

Hi Experts ,
Hi ,
I need to configure partner profile with a external system . I will be receiving customer data from the ext System .
I though of using msg type DEBMAS and msg type
and process code DEBM. I see its uses function module IDOC_INPUT_DEBITOR.
So what exactly this function module does ?
I was wandering if I need to create new Process code / Function Module .
My requirement is receiving the customer data along with address , shipping informations , customer no . So that when I drop orders its becomes available.
Thanks
MM_sD

Hi ,
Check all the settings needed for an R/3 - XI- R/3 scenario..... In ur case R/3 to XI is working fine and u have to check the XI-R/3 side.
Check the RFC destination ( Both in XI and in R/3)
Check the logical system name
PORT, Partner profile .....
Regards,
Jude

Similar Messages

Settings for IDoc Processing Maintain Partner Profile Manually

Hi Everybody,
I just wanted to maintain a partner profile for IDoc Outbound Processing in CRM7.0. The Partner Type is LS (Logical System).
Now, when I'm creating an Outbound Parameter and want to save, I get an Error Message that the field package size must be > 0.
The problem is, that there is no field Package Size. In older systems there is such a field under the field receiver port.
Anyone any idea where is the missing field or another solution.
Thanks and regards,
Sebastian
PROBLEM SOLVED !!
When you get the error message, press enter several times and the field appears. Incredible.... but true.
Edited by: Sebastian Wilhelm on Sep 3, 2009 4:06 PM

Hi,
Steps to do ALE Configuration with respect to IDOC:
Configuration in R/3:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using we21 and refer the port to the created RFC dest in above Step.
3. Create a Logical System using Transaction BD54.
4. Create a partner profile using transaction WE20.
Also need to configure in XI:
1. Create a RFC destination using Transaction = SM59
2. Create the ports using Transaction IDX1 and refer the port to the created RFC dest in above Step.
3. The port has to be displayed in the IDX2 transaction and we should be able to view the idocs which we imported through integration repository otherwise we have to manually import the idocs from IDX2 using the port created above
Also refer to the link below for further details:
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
Regards,
Nithiyanandam

Partner profiles issue

Hi All,
We are trying to sett the partner profiles for source systems.Able to do RFC connection.But not able to see data.
Thanks
Sidd

hi
are you able to jump from BW to R/3?? through sm59??
are you able to see data in rsa3 of your R/3 system...
If it is ok,you should see the data in bw..
Teja

Partner profile not available.

Dear Folks,
i am doing the scenario JDBC to IDOC. For that i did all the necessary ALE settings and configured the systems. While executing that scenario. In we02, i am getting the error partner profile not available eventhough i configured it. From the error i found that, in technical info, partner number and port are different. And i am getting some Default parnter number and port.
From my observations, i checked the Sender business system and i found that, logical system which was mentioned for this business system is replicating as a default parnter number in the technical info.
please guys i need your valuable suggestions to eradicate this error.
Regards,
Dileep

Hi Mark,
I checked the payload and i am not using header mapping.
I tested the same by doing some modification like, In sender business system, i replaced the default logical system name with which i am using.Then idoc status is changed to status 50. But i am getting the Default port as previously said.
one more thing is , whenever i am getting this partner profile error, it is hitting one of my Company portals. i.e., displaying this partner profile issue in MSS(managerial self service) of HR Portal.
I was little bit confused of why it is hitting the portal?
what would be the key point for their connection?
Please help.
Regards,
Dileep

In-House Cash current account check processed by Partner Type = GP

Hi,
We configured our IHC system so that the PAYEXT the IHC system receives are processed by Partner Profile-Partner Type = GP = Business partner.
In this we like to control that the current account send by the Payer = Business partner matches the entries in table IHC_TAB_APM_TT ( IMG : In House Cash - Account Management - Payment Processes in In House Cash - Define Transaction Type for Automatic Payments).
If no match is found the IDOC should error.
Hope somebody could advise on this.
Marcel Fonhof

Hi Siva,
As far as I know, a Java program will not allow a secure page to load without the certificate on client side (i mean u cannot even load even https://sdn.sap.com without its certificate). So, please check the certificates on the xi server present on the web server (https).
Best regards,
Felix

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code 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 XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (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.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(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)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (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
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

WE20 - partner profiles: inbound parameters - how to determine process code

Running standalone scenario on SRM 5.0.
First of all, it is not possible to "generate partner profiles" automatically in BD64 (distrubution model) in the backend system for message types:
BBPIV, BBPCP, ACC_GOODS_MOVEMENT, ACLPAY and MBGMCR.
The following error is displayed:
BBPCO
Inbound parameters for message type BBPCO could not be created
Enter a valid process code
etc.
When trying to create partner profiles manually in WE20, how do I determine the process codes for the different message types?

Note 330401 - Process code does not exist f. BBPCO01, BBPIV01
Solution
Check and if necessary, correct the following entries:
1. Assign function module to message type
Transaction WE57
The following entries are required:
Module IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO
Type F F
Basic type BBPIV01 BBPCO01
Msg type BBPIV BBPCO
Direction 2 2
Object type BBPBUS2081 (not for Release 3.1)
Note that object type BBPBUS2081 is not defined in Release 3.1*. In
this case, the 'Object type' entry remains empty.
2. Characteristics of inbound function modules
Transaction BD51
The following entries are required:
Inbound FM IDOC_INPUT_BBP_IV IDOC_INPUT_BBP_ACC_PO
Input type 1 1
03.09.2008 Page 2 of 3
Note 330401 - Process code does not exist f. BBPCO01, BBPIV01
Dialog allowed No No
3. Create the missing process code with Transaction WE42 (change inbound
process code). You can name the process code whatever you want. 'IV01'
or 'CO01' are examples.
The entry should look like this:
Process code IV01 (CO01)
Description BBPIV (BBPCO) inbound invoice
Option ALE Processing with ALE service
Processing Type Processing by function module
Save the entry. You are then on the detail screen. Enter:
Module (inbound)
Function module
IDOC_INPUT_BBP_IV (IDOC_INPUT_BBP_ACC_PO)
Application object
Object type
BBPBUS2081 (- no entry -)
4. Maintain the process code that has just been created in the partner
profile for the logical system.
Transaction WE20
Partner type 'LS'
regards
Muthu

Define Port, Partner Profiles, Process Code

Hi All,
Please provide the following valueble information
Define the below and why do we create them?
1. Port
2. Partner Profile
3. IDOC type and IDOC
4. Process Code
5. Message Type
Thanks and Regards
Sowjanya

>>1. Port
Ports are channel through which idocs are exchanged.
>>2. Partner Profile
Partner Profile specifies the kind of message that we are going to exchange with our business partner
>>3. IDOC type and IDOC
IDoc type defines the structure of the idoc. IDoc is a container which carries the data from one system to the another.
>>4. Process Code
Process Code refers to inbound function module which will read the data from the idoc and post it in the system.
>>5. Message Type
Message Type defines the kind of data that you are exchanging with your business partner.
Cheers,
Hakim

Issue in Partner Profile config for Outbound IDOC

Hi Experts,
I have requirement like, When ever there will be any change in a Sales Order an Outbound IDOC will get triggered though a output type. This IDOC will save a file in the Application Server.
The Message Type i am using is ORDERS and the Basic Type is ORDERS05.
I have created a Partner Profile also a Receiver Port of type FILE.
I have Assigned Message type in Outbound Parameters.
I have assigned Receiver Port and Basic type under "Outbound Option".
I have Assigned Applications as 'V', Message type as 'Output Type' and Process Code under "Message Control".
When i am changing any Sales Order no IDOC is getting Triggered. I checked the Sales Order>Extras> Output> Header> Edit, the Output type is in Status RED with Message " No Partner Profiles (Message Control) Maintained".
Please guide me if i have missed any configs.
Help me solving this issue.
Thanks in Advance!
Priyabrata

Hi Priyabrata,
please try changing in your partner profile the application from V to V1. Another problem that's often causing the partner profile not to be found are the partner functions that are added automatically by SAP, but sometimes forgotten in the partner profile.
I don't have a SAP system at the moment, but as far as I remember the long text of the message indicates the partner profile parameters that SAP uses for the lookup.
If all of this doesn't help, I'd quickly debug this and see why SAP's not picking up the correct partner profile.
Cheers, harald

EDI Partner Profile creation at Transaction Code FI12

How is the partner profile created when you select the Icon Partner Profiles, which is transaction code WE20 that is accessing from transaction code FI12.
The type is B for bank. Can the partner number be a end user defined number? Can this be the vendor number for the bank? That does not appear to be an option!
Here are my questions of the Post processing permit agent design.
How are the values for the "Types" created?
Thanks
Chris Courter

Rohan Patil wrote:>
> BEGIN = 1.
> edi_dc40 segment values
> SEGMENT = 1.
> TABNAM = EDI_DC40.
> MANDT = 120.
> DIRECT = 2.
> IDOCTYP = CREMAS05.
> MESTYP = CREMAS.
> SNDPORT = SAPNBD.(XI port)
> SNDPRT = LS.
> SNDPRFC = LS
> SNDPRN = NXICLNT120.
> RCVPOR = SAPNED.(ECCport)
> RCVPRT = LS
> RCVPFC = LS
> RCVPRN = ECCCLNT120(ECC partner number).
Hello Rohan,
IDocs SNDPRN/SNDPRT/MESTYP will be taken in SAP for processing the received IDOC,so in your case either you need to create the partner profile NXICLNT120 with all inbound details or need to change the same in mapping and pass the values of your partner in SNDPRN SNDPRT fileds of control record
HTH
Rajesh

Issue !!! Partner Profile Creation Using EDI !!!

Hi!
   Can anyone tell me whats the use of <b>Message Code & Message Function</b> for Creating Partner Profiles using<b> EDI</b>
    Transacion WE20 for EDI.
   Thanks.

Hi,
These fields can be used to differentiate between processing of the same message type. You can create several partner profiles using the same message type. By populating these fields, you are able to assign different process codes. Otherwise you are only allowed one entry for the message type.
For example, you need to setup two inbound partner profile for delivery advice. One is dealing with incoming shipment (process code DELS) and the other one dealing with purchasing (process code DESA). Both are using same message type DESADV. If you did not specify message code or message function. They system will allow to setup only one inbound message type for DESADV and not for two entries in inbound partner profile. For this case, you need to populate both the message function fields, for example SHP (Shipment) and PUR (Purchasing).
By doing these, system will allow you to assign different process codes for same message type.
Also these will allow you to split/group the IDocs processing (running parallel).
For example, if you want to post the incoming above message types, you can use standard program RBDAPP01 to process and running parallel by specify message function in selection screen or you can setup different variants to run in the background.
Regards,
Ferry Lianto

Partner profile not maintained error while testing inbound processing

Hi gurus,
I am trying to upload a customer master data using LSMW idoc method, I followed all the required steps and then I tried to test the inbound processing using T.code we19 and there i gave my basic type as debcor01 and I clicked on standard inbound test but it gives me an error which says partner profile is not maintained, but I have maintained the partner profile and assigned the same in LSMW. So anyone of you can please help me to solve this problem.
thanks,
Rajeev

Rajeev,
Check whether the Account Category is mantained properly or not.
K.Kiran.

ALE issue:No partner profiles (message control) maintained

Hi,gurus:
My ALE scenario is tranferring PO from client 800 to 900 client.
Now the logical system,partner profile，port，rfc，distribution model are created both the sender and receiver side.
In ME21N->MESSAGE, the output type is NEU,and medium is A,partner function is LS,partner is ECCCLNT900.
When I saved the PO,the status is red,and no idoc was generated.
I viewed the processing log,the information is: No partner profiles (message control) maintained.
But my distribution model is sender:ECCCLNT800;receiver:ECCCLNT900;MESSAGE：ORDERS;
The partner profile is ECCCLNT900(LS),and the outbound parameters are ORDERS,SYNCH. For ORDERS,the message control is EF,NEU,ME10.
Have you ever met this issue?
Thanks in advance.

Hi Li,
Please refer this threads...
Re: Message is not proposing automatically
Re: IDoc was saved but cannot or should not be sent
Hope you have to post this thread in ABAP General category..
Regards,
kumar.

Could any body tell me the significance of Partner Profiles in IDOC PROCESS

Hi,
Could any body tell me the significance of Partner Profiles in IDOC process.
Thanks in Advance,
BSV.

Hi,
The partner profile is used to validate the sender and receiver system for a given message type and to assign to the correspondence process code (function module) to post the IDoc to application system.
This applies for both Inbound and Outbound IDOC's.
Also please check this link for more information.
http://help.sap.com/saphelp_46c/helpdata/en/dc/6b803343d711d1893e0000e8323c4f/frameset.htm
Regards,
Ferry Lianto

File to IDOC - issue with partner profile

I have done File to IDOC scenario and tested it end to end successfully. For same have done all require configuration setting in R/3 like defining logical System and partner profile. And it sends new IDOC successfully in R/3 with status code 50 (IDoc added).
But when I create new logical system and partner profile in R/3 and when I use same logical system in my above mention scenario then my new generate IDOC in R/3 return status code 56 (EDI: Partner profile inbound not available). But same scenario work fine with my earlier partner profile. Here I have done all require changes at adapter level like adapter specific identification and same new logical system I have update in SLD with my business system Logical System Name.

Hi Bhavesh,
Thanks for your reply.
In control record, I checked with sender and receiver partner. In this sender partner is new partner profile which I have created with port details. Receiver partner has logical system name which I have mentioned in my SLD for my receiver business system. But in receiver partner dont have any port details.
But still it has same problem.
-Sunil

Process code & Partner Profile Issue

Similar Messages

Maybe you are looking for