Guidance for ALE-IDOC scenario

Hi all,
Please consider the senario:
Idoc is triggered from sending system to receiving system.But receiving system is not available/Down.
Can you please guide me how to handle this scenario as data is not created at receiving side.
I am also not able to identify which exact idoc from sending side hasn't reached receiving side as all the idocs triggered in the whole day (including the idocs triggered when receiving server is down)are GREEN.
Thanks.

Hi,
You can check the status of your idoc from tcode WE02 or WE05.
whether it is successfully sended or not and if not then with the error
message.
Hope it helps
Regards
Mansi

Similar Messages

Getting Error 26 in ALE IDOC scenario .- EDI Syntax Check Error...

Hi..
i am working in ALE Idoc scenario...I am getting Status 3 as well as status 26 in we02 transaction in my custom IDOC scenario for outbound process..
The error is 'EDI- SYntax Check'..
How to remove this error..
Pls help.

ya, there is only one segment available in IDOC..named i.e zseg_a .
So , error in postion is avoided..
How to find syntax error then?

Technical requirement's for ALE/Idoc

Hi all,
Am new for ALE/IDOC
we have requirement for ALE inbound and outbound scenarios ,
what are the mandatory requirements(port,partner profile, message type ..etc) from technical point of view for Technical consultants,
Regards
Suresh.D

Here is the step-by-step configuration approach in ALE.
- Create logical system (txn BD54)
- Assign client to Logical system (txn SCC4)
- Create RFC destination (txn SM59)
- Generate ports (txn WE21)
- Create partner profiles (txn WE20)
- Create distribution model (txn BD64)
Now you can use the required transactions like BD10 (to send materials), BD12 (to send customers), BD14 (to send vendors)....which would create the IDocs. You can view the generated IDocs via txn WE02 as you note down the system time when the IDocs are generated. You can use txn BD87 too to trace the IDocs at the sender...
If idoc is in status 51 or 52 process by program RBDMANI2 or in transaction BD87, If idoc is in 64 status process the idoc by program RBDAPP01.

Material for ale,idoc programming

Hi folks,
i need urgently the material for IDOC programming.i am mentioning the process below.
1)i have created one program. i need to send some fields to a folder through IDOCS.
when i will press a push button on my program, this idoc program should execute so that some of the fields will transfer through IDOCS.
Thanks

hi,
Intermediate Documents (IDOCs)
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.
The two available process for IDOCs are 1) Outbound Process 2) Inbound Process.
There are basically two types of IDOCs.:
1. Basic IDOC type defines the structure and format of the business document that is to be
     exchanged between two systems.
2. Extension Idoc: Extending the functionality by adding more segments to existing Basic IDOCs.
-To Create Idoc we need to follow these steps:
1. Create Segment      ( WE31)
2. Create Idoc Type      ( WE30)
3. Create Message Type ( WE81)
4. Assign Idoc Type to Message Type ( WE82)
1. Creating a Segment:
nGo to transaction code WE31
nEnter the name for your segment type and click on the Create icon
nType the short text
nEnter the variable names and data elements
nSave it and go back
nGo to Edit -> Set Release
nFollow steps to create more number of segments
2. Create Idoc Type      (WE30)
nGo to transaction code WE30
nEnter the Object Name, select Basic type and click Create icon
nSelect the create new option and enter a description for your basic IDOC type and press enter
nSelect the IDOC Name and click Create icon
nThe system prompts us to enter a segment type and its attributes
nChoose the appropriate values and press Enter
nThe system transfers the name of the segment type to the IDOC editor.
nFollow these steps to add more number of segments to Parent or as Parent-child relation
nnSave it and go back
nnGo to Edit -> Set release
3. Create Message Type (WE81)
nGo to transaction code WE81
nChange the details from Display mode to Change modenAfter selection, the system will give this message The table is cross-client (see Help for further info). Press EnternClick New Entries to create new Message Type
nFill details
nSave it and go back
4. Assign Idoc Type to Message Type (WE82)
nGo to transaction code WE82
nChange the details from Display mode to Change moden After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
nClick New Entries to create new Message Type.
nFill details
nSave it and go back
There are three types of records :
nControl Record                          nData Record                                     nStatus Record
Control Record - contains the key information like destination, IDoc type, message type, port and sender information. Control records are of EDIDC type of structure.
Data Records - This contains two parts.
nAdministrative Section and Data Section
nAdministrative Section consists of Idoc number, Segment Name, Segment number, Version, Segment Hierarchy etc.
nData Section contains the data of respective segment
nData records are of EDIDD type of structure
nStatus Record - whenever a process is taken place, system will generate status records.
nWe can identify the process with the number of status record.
n01 - 49 for Outbound Process
n50 - 75 for Inbound Process
nwhen IDoc is processed the messages are:
n01 - IDoc is created
n30 - IDoc is ready for dispatch
n03 - IDoc is processed
check all the below links u will find lot of info
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
For ALE -- IDoc's
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
ALE/ IDOC/EDI
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.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
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
http://www.angeli.biz/www5/books/IDocBook/IDocBook.pdf
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
~~Guduri

Upgradation procedure for ALE/IDOCS

Can anyone let me know what is the upgradation procedure for ALE/IDOCS and what are the steps needs to be checked out during technical remediation part of version upgrade(lower version to ECC6.0)?

IDocs are backwards compatible, so I don't think you need any special procedures for them, just a regular test, to make sure everything stull works fine. If you've had extended any standard IDocs, that part will need to be reviewed, as any other custom development.
However, there might be a newer version of the IDoc type available in ECC 6.0, which you didn't have in the previous release. You might want to see if there would be any benefits in switching to the newer version.
I'm sure you'll find all the information on the Upgrade page on SAP's [web site|http://service.sap.com/upgrade]. Also there is an SAP Press book on the subject.

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
<b>*reward for useful answers*</b>

ALE Settings For File-IDOC Scenario

Hi All,
While Doing IDOC-File Scenario we have to do the Following Settings
In XI
1) Create RFC Destination towards R/3
2) Create Port
3) Load Meta data
In R/3
1) Create RFC Destination towards XI
2) Create Port
3) Create PF
Q1) Coming to File-IDOC Scenario do we need to do the Same Settings ????
Q2) In this File-IDCO Scenario do we need to create RFC Destination in R/3 towards XI ????
Clarify me these Confusions
Regards
Bopanna

HI,
for IDOC TO FILE
We need to create the rfc destination at XI side so as to send the acknowledgement to sap r/3 as soon as idoc has been received.This is the reason WHY WE NEED RFC DESTINATION AT XI SIDE
There are are only 2 major difference in Ale settings for FILE TO IDOC AND IDOC-FILE
i.e for FILE-IDOC
1) No need to Distribute the modal view
2) For partner profile Specify the INBOUND PARAMETERS
FOR STEP BY STEP U CAN SEE THE SETTINGS GIVEN BELOW
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
ALSO WE NEED TO CONFIGURE THE IDOC ADAPTER AS RECEIVER TO CONVERT THE IDOC-XML TO IDOC
PLZ REFER THE LINK BELOW.
PLZ REWARDS THE POINTS
VIKAS JAIN
                                                                                [https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098]
Edited by: vikas jain on Jan 22, 2008 11:49 AM

Steps for ale idoc creation?

Hi,
I want the complete process of ale idoc generation.
my maild id is [email protected]
Thank You.
From:
Mohammed Moid Ahmed

Hi
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
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Reward points if useful
Regards
Anji

Tech spec for ale idoc

hi all
can anyone give technical specification format of ALE and standard IDOC
regards
shankar
mail to my id [email protected]

HI
GOOD
ALE->
TABLE OF CONTENTS
1 Introduction to al
1.1 What is ALE?
1.1.1 A Summary
1.1.2 Mass Processing Of IDocs
1.1.3 Cross-System Document Trace (Audit)
1.1.4 Error Handling
1.1.5 What can be distributed?
1.2 Why ALE?
1.2.1 The SAP Solution - ALE
1.3 Phases in an SAP project
1.4 Phases in an ALE project
1.4.1 Phase 1: The Assessment and Project strategy phase
1.4.2 Phase 2: The Design phase
1.4.3 Phase 3: The Configuration phase
1.4.4 Phase 4: The Development phase
1.4.5 Phase 5: The Operations phase
2 Project phase 1: ALE Assessment
2.1 Setting up the project team
2.2 Project team tasks
2.2.1 Assess business requirements
2.2.2 Assess ALE and determine gap
2.2.3 Confirm data / function distribution requirement
2.3 Project team deliverables
2.4 Obtain programme sign-off
3 Project phase 2: ALE Design
3.1 Project team tasks
3.1.1 Develop standards & procedures early
3.1.2 Distribution settings
3.1.3 Design for flexibility
3.1.4 Audit
3.1.5 Technical impact
3.1.6 Sign-off
3.2 Deliverables
4 Project phase 3: ALE Configuration
4.1 Project team tasks
4.1.1 Confirm business requirements
4.1.2 Configure ALE basis area
4.1.3 Functional configuration
4.1.4 QA & testing
4.1.5 Sign-Off
4.2 Deliverables
4.3 Other issues
5 Project phase 4: ALE Development
5.1 Project team tasks
5.1.1 Functional specifications
5.1.2 Technical specifications
5.1.3 Development
5.1.4 Quality assurance and testing
5.1.5 Business sign-off
5.2 Deliverables during this phase
6 Project phase 5: ALE Ops Support
6.1 Project team tasks
6.1.1 ALE Administrator role
6.1.2 Capacity plan
6.1.3 ALE Operations role
6.1.4 ALE Failure recovery
6.1.5 ALE Support organisation structure and process
6.2 Other considerations
6.2.1 Client copies
6.2.2 Client specific configuration
6.2.3 Error handling
6.2.4 ALE specific scenarios
6.3 Deliverables
GO THROUGH THIS LINK
http://www.sapgenie.com/ale/whitepaper.htm
IDOCS->
http://www.icoresolutions.com/company/downloads/iCIS_technical.pdf
http://www.sapgenie.com/sapgenie/docs/interface_function_specification.doc
THANKS
MRUTYUN

How is partner profile for ALE/IDOC transported?

Hi experts,
How is a request created for transporting configurations in ALE/idoc.
Valuable answers will be generously rewarded.
regards,
Shrita.

Hi,
some configurations are client dependent and some are client independent.
so client dependent configurations are transported to different clients using SCC1 transaction.
and client independent configurations they refelect automatically.
Regards
vijay

Best practise for EDI-IDOC scenario

I want to create a EDI-IDOC scenario for invoicing our customers.
There are 2 options that I can use, create partner profiles of type KU for each of our customer that we will be invoicing or have
a LS for XI and configure the same.
My company has around 400 customers. So incase i chose to go with KU then i have to configure 400 partner profiles right?
Which is the best practice for this scenario?

As stated above, you can use LS partner instead of KU partner. There are, however, some pros and cons to be considered:
1) Post-processing agent assignment. If you have different people working with different customers you can assign them as post-processing agents to the respective partner profiles. If you switch to LS you will need to have only one agent (it might be a group of people though).
2) When you have a separate profile for each customer then the customer number is included in the IDoc control record. This allows to quickly view the IDocs by customer number. E.g. if a customer calls and asks where the heck is my document then customer service could easily see all the IDocs for that customer in WE05, for example, and check what's going on. With LS they would have to dig into the segments for that.
So the business process requirement decides this. If you don't care for any of this you might be even better off using LS instead of KU, because it requires less maintenance.

Need slide for ALE & IDOC

Dear friends,
I have to take Trainning session for freshers in my company ,
if any body havinig ALE & IDOC slides pls send to my mail ID
[email protected]
today i have to do this task..
thanking u..
regards
veera

Hi Veera ,
You can refer to below links for more detailed reference.
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
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
http://www.sapgenie.com/ale/why_ale.htm
http://www.sapdevelopment.co.uk/training
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
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
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
Hope this helps
Regards.
Note:- Reward if useful

Performance improvement for ALE/IDOC processing

Dear experts,
Could you let me know any information to tune performance?
In our system (SAP R/3 Enterprise 6.20), material master data is distributed from one client to other clients in the same instance. It is because material master is maintained centrally, and is distributed to other clients for member companies.
During the night batch, distributing master data takes more than 2 hours. Although the distribution usually finishes without errors, we would like to explore ways to improve processing performance. Especially, program RBDMIDOC runs long time to create IDOC for MATMAS, even 0 master IDOC is set eventually.
OSS notes of the list for OS/DB/SAP parameters related to ALE/IDOC, tips in organizing batch jobs, etc, will be very appreciated.
Many Thanks,
Nori

I'd recommend to profile the program at least once to see where there's possible room for improvements. I.e. an ABAP runtime analysis and SQL trace would be good for a start. You can check out the links in thread Please Read before Posting in the Performance and Tuning Forum, which will give you some references if you need them. Once you have more details, you either know what you need to do or you can provide them and ask a more specific question (and thus you will receive much better answers).
As a general remark though I've seen often poor performance initially on the changer pointer selection, because there are too many entries in the table (due to system generating unnecessary change pointers, which should be disabled or/and lack of proper reorganization, i.e. deletion of old/processed change pointers via BD22). Sounds like this is most likely also the cause of your problem, because otherwise it's hard to explain long run times without generating any master IDocs. You can check the number of change pointers easily via view BDCPV or BDCP2 - it depends how you store your change pointers (most likely you find them via view BDCPV in a 6.20 system, unless somebody switched it to the newer BDCP2).
If you still have them in BDCPV (or the underlying tables to be more precise), check out [OSS note 305462 - MOD: Migration change pointer to table BDCP2|https://service.sap.com/sap/support/notes/305462], which will provide you a general hint how to do that (and thus also improve the performance). However, if you're currently not deleting any old change pointers, you should ensure that a regular job runs for transaction BD22 (program RBDCPCLR). You'll easily find other (possibly relevant) OSS notes by doing a search yourself...

Document need for ALE-IDOC's

Hi folks,
I am new to the area of ALE-IDOC's .
could you please provide the document for that if possible.
I want the manual steps for that with transaction codes.
Could you please provide the documentation alone for the IDOCS.
Thanks & Regards,
Surendra

Hi,
Please refer following links,
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE%2CIDOC
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE+IDOCS
http://wiki.sdn.sap.com/wiki/display/ABAP/OutboundIdocThrough+ALE
Thanks & regards,
ShreeMohan

Document for ALE-IDOC

Hi All,
I m new to ALE-IDCO.
Can u plz give me documents or link to the document related to ALE-IDOC.
Is there any Video or E-learning for avilable for learning ALE-IDOC?
Thanks & Regards
Sachin

http://www.sdn.sap.com/irj/sdn/ale
ALE configuration procedure
ALE/IDOC Material
ALE Idoc pdf
thanks
anurag

Guidance for ALE-IDOC scenario

Similar Messages

Maybe you are looking for