Inbound idoc

[Former Member]

Hi,

Can anybody helps to send me an Inbound idoc procedure ,if possible with a sample Program.

Thanks,

Arun .

[Former Member]

Hi,

Can anybody helps to send me an Inbound idoc procedure ,if possible with a sample Program.

Thanks,

Arun .

[Former Member]

Hi,

I have good document on this along with screen shots. Please give ur mail id, so that I can forward it to you.

[Former Member]

refer below link

https://www.sdn.sap.com/irj/scn/wiki?path=/display/snippets/converting%252bsapscript%252boutput%252b...

[Former Member]

please do search in SDN before posting

[Former Member]

Hi,

Hope this link will help you.

[link1|]

Thanks,

Asit Purbey.

Edited by: Asit Purbey on May 22, 2009 6:08 AM

[Former Member]

Outbound idoc procedure: 1. Creating logical systems: TCode is BD54, 2. Assigning appropriate client: SCC4, 3. Create RFC Destination: SM59, 4. Port Creation: WE21, 5. Partner Profiles Creation: WE20, 6. Disribution Model: create, generate & distribute (TCode: BD64), 7. Consistency Check: BDM5

Inbound idoc procedure: 1. Creating logical systems: BD54, 2. Assigning appropriate client: SCC4, 3. Partner Profiles Creation: WE20.

In Inbound side, Process Code is mandatory. WE42--Inbound Process Code

In Outound side, Port is mandatory. Also we have IDoc Type, EDI Structure.

WE81create message type--required in both Outbound & Inbound side

WE82for IDoc type & message type relationshiprequired in both Outbound & Inbound side

WE31--for segment type relationship, segment creation

Outbound Process--Determine receiver, Segment filtering, Field Conversion, Version Conversion

Inbound process---Version Conversion, Segment filtering, Field Conversion

Serialization--extra in Inbound process

WE47--- gives full list of IDoc Status

WE60--IDoc Documentation

BD64- IDoc Filtering

BD56- Segment Filtering

BD55- Field Conversion

BD62- Relationship b/w Conversion rule & segment

BD79- (Actual values we are going to send in Conversion Rule) Segment, Conversion rule

BD44- Serialization Groups---implemented in Inbound side

BD102- ALE: Outbound Channel Registery

BD103- ALE: Inbound Channel Registery

Outbound Status T Codes: Status 42-when we create Idoc with test tool (WE19), Status 01Idoc created, Status 29ALE Service Layer error, Status 26Syntax error issue, 25forced along with syntax errors, 30Ready for dispatch to partners, 03Idoc with port, 12Idoc dispatched already

(inbound system)

Inbound Status T Codes: Status 50when added into Inbound system, ALE Service Layer error65, Syntax errors-60, forced along with syntax errors61, Ready to pass to ALE Service layer-64, Serialization info. needed, actual Idoc will wait-66, Ready to pass to Application layer-62, Incomplete posting--52, Data/logic issues51, Successful implementation (Application document posted)--53,

status 68--u can't clear it, needed to recreate Idoc from inbound side, Status 74-Idoc created by test tool, 58---transactional RFC

Batch processing:

RBDAPP01 ALE inbound processing

RBDMANI2 ALE inbound error reprocessing

All TCodes related to IDoc: WEDI

[Former Member]

[7 Steps For ALE Configuration|https://wiki.sdn.sap.com/wiki/display/ABAP/7StepsForALEConfiguration]

[Modify IDOC Status by Program |https://wiki.sdn.sap.com/wiki/display/ABAP/ModifyIDOCStatusbyProgram]

[IDOC Steps|https://wiki.sdn.sap.com/wiki/display/ABAP/IDOC+Steps]

[Former Member]

Hello,

Basically Idoc is a intermediate document to exchange data between two SAP system.

We can create in the following ways -

WE30 - create a IDoc type

WE31 - create segment

WE81 - Create message type

WE82 - Assign Idoc type to message type.

Above are teh main transaction to create IDOC .

Regards

Sathish

[Former Member]

Hi,

In simple, this is what an inbound process is all about.

- Store the IDoc in database

- Invoke the posting module

- Create the document

What actually happens during the inbound process is that,

- Remote system calls IDOC_INBOUND_ASYNCHRONOUS and passes communication IDoc to the system

- User ID validations and authorizations are checked

- Data in the control record is validated against the partner profile

- ALE services: filtering, conversion and version change are carried out

- Application IDoc is saved in the database

- Checks if the IDoc is configured for "Process IDoc immediately"

-> If "no", Program RBDAPP01 released is executed and proceeds as per the next step

-> Else, follows the follwing step

- Reads the process code from the partner profile

- Process code points to the posting module

- Posting module creates the application document

~ Bineah

[soumya_jose3]

Hi,

Check the below links:

http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-ii/

http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-part-iii/

Regards,

Soumya.

[Former Member]

hi,

use this link hope it will help u .

.

[Former Member]

Outbound idoc procedure: 1. Creating logical systems: TCode is BD54, 2. Assigning appropriate client: SCC4, 3. Create RFC Destination: SM59, 4. Port Creation: WE21, 5. Partner Profiles Creation: WE20, 6. Disribution Model: create, generate & distribute (TCode: BD64), 7. Consistency Check: BDM5

Inbound idoc procedure: 1. Creating logical systems: BD54, 2. Assigning appropriate client: SCC4, 3. Partner Profiles Creation: WE20.

In Inbound side, Process Code is mandatory. WE42--Inbound Process Code

In Outound side, Port is mandatory. Also we have IDoc Type, EDI Structure.

WE81create message type--required in both Outbound & Inbound side

WE82for IDoc type & message type relationshiprequired in both Outbound & Inbound side

WE31--for segment type relationship, segment creation

Outbound Process--Determine receiver, Segment filtering, Field Conversion, Version Conversion

Inbound process---Version Conversion, Segment filtering, Field Conversion

Serialization--extra in Inbound process

WE47--- gives full list of IDoc Status

WE60--IDoc Documentation

BD64- IDoc Filtering

BD56- Segment Filtering

BD55- Field Conversion

BD62- Relationship b/w Conversion rule & segment

BD79- (Actual values we are going to send in Conversion Rule) Segment, Conversion rule

BD44- Serialization Groups---implemented in Inbound side

BD102- ALE: Outbound Channel Registery

BD103- ALE: Inbound Channel Registery

Outbound Status T Codes: Status 42-when we create Idoc with test tool (WE19), Status 01Idoc created, Status 29ALE Service Layer error, Status 26Syntax error issue, 25forced along with syntax errors, 30Ready for dispatch to partners, 03Idoc with port, 12Idoc dispatched already

(inbound system)

Inbound Status T Codes: Status 50when added into Inbound system, ALE Service Layer error65, Syntax errors-60, forced along with syntax errors61, Ready to pass to ALE Service layer-64, Serialization info. needed, actual Idoc will wait-66, Ready to pass to Application layer-62, Incomplete posting--52, Data/logic issues51, Successful implementation (Application document posted)--53,

status 68--u can't clear it, needed to recreate Idoc from inbound side, Status 74-Idoc created by test tool, 58---transactional RFC

Batch processing:

RBDAPP01 ALE inbound processing

RBDMANI2 ALE inbound error reprocessing

All TCodes related to IDoc: WEDI

Edited by: Niharika Singh on May 26, 2009 4:38 PM