Partner Profile settings for IDOCs

Hi,
when i posted the IDOC, it left the status 51.
i think which means "Application not posted".
do i need to change the partner profile!
if yes please let me know how to change that.
its very urgent please.
thanks in advance.
Regards,
ravi.

As mentioned in the earlier reply you need to check idoc listing WE02.
You may also want to look into the partner profile- WE20 and see if what you are trying to pass thru has been set up correctly. Make sure the correct port is defined along with the partner details.
If you need to edit the IDoc , you can do it from WE02 by clicking on the segment and then going into the Change mode. The other option of re- processing Idocs is using the testing tool- WE19 or the re-process Idocs BD87 transactions.

Similar Messages

Partner profile settings - Trigger Immediate or Collect Idocs ??

Hi All,
We have EDI Setup between SAP and a EDI system and Idocs flowing with port type TCP/IP connection.
we are facing issue at some times where in the Idoc is created and is in status 03 / 12 (trfc queue is cleared) but not found in the EDI system.
what I have observed is the issue has occurred for only few vendors where partner profile setting in trigger immediately
and it has not occurred t for every Idoc created, only some Idocs were missing in EDI system.
issue was not present in case where partner profile setting in collect Idocs.
So it that do we have a best practice to set partner profile to collect Idocs (packet size ~ 20) when sending to EDI subsystem?

Hi,
It seems the issue is not because of your partner profile setting since your status of the IDOC is 03 0r 12.
Output mode 'Transfer Idoc Immediate': Single Idoc is transfered immediately to the EDI system when the output triggered
'Collect Idoc': Idocs generated for the particular message type will be collected in a single file and are triggered to EDI system at a scheduled time. Here no of Idocs sent in a file will be decied based on packet size.
It may be problem with your network connectivity.If are using a EDI substem then you use file port not trfc port.
Check how the EDI sytem is reading the Idoc files which are created in R/3 OS level is it through FTP???
Regards
Praveen

R3 settings for IDOC-IDOC scenario

Hi,
For IDOC to IDOC scenario what are the settings we have to in R3 System other than XI configuration settings.
What are setting for both sender and receiver side.
Thanks,
Kishore

Hi Kishore,
http://help.sap.com/saphelp_nw04/helpdata/en/18/22b800773211d396b20004ac96334b/content.htm
http://www.erpgenie.com/index.php?option=com_content&task=view&id=346&Itemid=57
http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci994575,00.html?NextURL=http%3A//searchsap.techtarget.com/expert/KnowledgebaseAnswer/0%2C289625%2Csid21_gci994575%2C00.html
http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
Refer this material..
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
You can directly create an iDoc using some transaction like...
Use TCODE bd10 - to Send Data
and TCODE bd11 - to Get Data
and you can check the IDoc List using TCODE we02.
As you want step by step procedure.
1. Define Logical System and Assign Logical System
TCODE sale
2. Define RFC
TCODE sm59
3. Define Port
TCODE we21
4. Define Partner Profile
TCODE we20
5. Define Distribution Model
TCODE bd64
6. Send Data
TCODE bd10
7. Get Data
TCODE bd11
8. IDoc List
TCODE we02
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Create IDOC Type
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
u can also check all these links related to idocs
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
Reward points if this helps
Regards
Pragathi.

Partner profile details for WBI

Hi all
    this is my requirement.we need to send a file from WBI to SAP as IDOC.i want to know about sender details(i.e) sender port ,sender address,partner number.just suggest me about these things
    Thanks in advance

Hi ,
          Please refer the folowing links
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
Configurations in R/3 side
1. SM 59 (RFC destinations)
Create a RFC destination on the XI server. The connection type should be R/3 connection. The target host needs to be the XI server.
2. WE 21 (Ports in IDOC processing)
Create a transactional port. Provide the RFC destination created in this.
3. BD 54
Create a logical system.
4. WE 20 (Partner Profiles)
a. Create a new partner profile under partner type LS.
b. Assign the message type in outbound parameters.
c. Open the message type (Dbl click) and configure the receiver port to the port created.
Configurations in XI server.
1. SM59 (RFC destination)
Configure the RFC destination specific to the R/3 system.
2. IDX1 (Port maintenance in IDOC Adapter)
Create a port and provide the RFC destination.
TESTING:
WE19 For pushing the idoc in xi through trfc port.
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Assign points if you found helpful
Regards.,
V.Rangarajan

Partner profile to send Idoc to PI 7.4 system from ECC

Dear Experts ,
Do we need a partner profile to send Idoc to PI 7.4 system from ECC.
or Just Port on TRFC is enough ..?
if i need to create a Partner profile ...how to define a logical system and how Assign Logical System to Client... when there is no client for JAVA only PI system ..?
thanks
Shakif

Hi Mohamed,
You need to create a tRFC port on sending ECC system. The RFC destination selected in this port os the one created for IDOC transfer.
Also you need a logical system, use client 000, i.e. PI1CLNT000.
At last you have to create a partner profile to define the IDOC type used.
Best Regards
Harald

Can I transport partner profile settings frm one system to other?

hello,
is it poosible that whatever partner profile settings i have maintained in development server that i can trasport into production server?
or i have to maintain it manually?

Hi,
Usually you have to maintain manually the partner profile in production system due to security and data integrity purposes.
For example, you don't want to send any testing data to your partners (vendor, customer, etc) and you want to make sure the interfaces (inbound and outbound) work properly and free errors.
Having said that you can distribute and generate partner profile (BD64) from DEV to QA without using transport system. Please ensure RFC connection are setup properly for DEV and QA systems prior to distribute.
Regards,
Ferry Lianto

Error : Pre Settings for IDoc inbound processing are missing error

Hi Experts,
There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
Thanks in advance.
Madhurima.

I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
[iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

Is it possible to transport partner profile settings ?

hello,
is it possible that whatever partner profile settings i have maintained in development server that i can transport into production server?
or i have to maintain it manually?

Hi,
Partner profile setting are actually soft configuration and you cannot transport them.
You have to set partner profile in all stages.
Nilesh

Partner profile settings.. for IDOC to File

i am trying to send Idoc to XI system from my r/3..
once iam sending from r/3 we19 ,i am getting error like this
receiver port " port name " does not exist in the table of port descriptions ..
how can i maintain receiver port in sender sys..?it is asking for RFC destination which is there in receiver sys but not in sender ....
how should i configure...
(Note: i have sent file to Idoc with same configuration settings..)
NOW
i am sending IDOC FROM IDES TO XI as FILE
Control record :in we19 ( IDES5.0)
   (XI-System)(SYS ID =O36)    (IDES5.0)(SYS ID = O20)
       Receiver:                      Sender:
port:SAPO20_800                 port:XI_00_800
partnerNo:036CLNT036        artnerNo:T90CLNT090
i have maintained outbound settings in T90CLNT090..
thanks in advance..
Ramesh..
THANKS FOR YOUR QUICK RESPONSES .HERE I added ALL DETAILS OF CONFIGURATION..from which iam getting error

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

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

ALE partner profile setup for diff. IDOC extension

Hi,
We have three extensions of IDOC type HRMD_A06 and message type HRMD_A. In one of the extensions segment IT0002 is extended.
In the partner profile extension is not specified. Due to this when the IDOC is generated Custom segment is not getting picked up.
I pu the extension in the partner profile then it woks fine.
But I do not want disturb the existing profile setup. Is there any option in WE20 where we can define two profiles with one message type, basic type and different extensions.
Also if we define the custom message type then distribution model and the partner profile needs to be generated for the new custom message type.
Appriciate quick response.
Regards,
Sonali

Hi,
just check the FM 'BAPI_BUPA_CENTRAL_GETDETAIL'.
Or just search for oher FMs with BAPI_BUPA*.
Hope this helps...
vasanth

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

FM to get partner profile details for ALE-IDOCs?

hi
is there any function module to get partner profile details in current system?
extremly sorry my mistake......
for ALE-IDOCs
Message was edited by:
 ashwinee mali

BAPI_BUSINESS_PARTNER_MODIFY CBP: BAPI for Modifying (Creating/Changing) Business Partner
BAPI_BUSINESS_PARTN_GET_DETAIL CBP: Business Partner Detailed Information
regards,
srinivas
*reward for useful answers*

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.

Partner Profile configuration for EDI 810

Hi,
I am configuring partner profile for EDI 810 (Invoice). In the message control tab, what values should be entered for
1. Application
2. Message Type and
3. Process Code
Thank you.

Hi,
- Check Transaction NACE to see what applicatios you can use for different objects.
- Check transaction WE42 for all outbound process codes
- Check transaction WE41 for all inbound process codes.
- Check transaction WE64 for inboud / outbound message types and related process codes.
EDI 850:
Application - EF
Process code - ME10
Message type - NEU ( or your custom message type setup for EDI )
IDOC - ORDERS01 to ORDER05
EDI 810:
Application - V3
Process code - SD09
Message type - RD00 ( or your custom message type setup for EDI )
IDOC - INVOIC01 , INVOIC02.
EDI 820:
i think this is for inbound idoc of Payment Order/Remittance Advice. When yuo setup inbound partner profile, you do not need to know application
Process code - LOBX
Message type - LOCKBX
IDOC - PEXR2002
Let me know if you need any other information.
Regards,
RS

Partner Profile settings for IDOCs

Similar Messages

Maybe you are looking for