BDC

[Former Member]

This is Ramana. I am searching for SD. i want to know BDC,ALE,IDOC

[Former Member]

Hi

Send a test mail st shesagiri@gmail.com , can send u detailed documentation

[Former Member]

Hi Naveen,

IDOC: Intermediate Document. It is nothing but a data holder.

o Transaction Codes:

 WE02 – To view the IDOC

 WE09 – To search for an IDOC based on data in the IDOC

 WE19 – Test tool to create and simulate an IDOC

IDOC is divided in to three parts.

• Control Record

• Data Record

• Status Record

Control record (Table: EDIDC):

- Every IDOC has only one Control Record

- Each Control Record contains header information like:

o IDOC Number

o Direction of IDOC: Inbound or Outbound

o Date and Time of creation of IDOC

o Date and time when the IDOC was last modified.

o Message Type of IDOC

o IDOC type and extension of IDOC

o Sender and Receiver Parner,

Data record – (Table: EDID4):

- Data Record contains Data to be processed.

- Every IDOC has one data record with multiple segments in hierarchy.

- Segments and Hierarchy of Segments are defined by IDOC Type and Extension. IDOC type and extension are explained in detail in further sections.

- IDOC created has to strictly follow the hierarchy, else IDOC fails with Syntax error.

- Segments which are repetitive has qualifiers attached to it. E.g. For inbound DELINS IDOC, segment E1EDKA1 contains partner information like sold-to, ship-to, supplier. How will you identify which E1EDKA1 contains which partner. They are identified through qualifier, like for sold-to, segment E1EDKA1, qualifier would be AG. For ship-to it is WE and for supplier it is LF.

Status record – (Table: EDIDS):

- Status Record describes the status of IDOC.

- Each IDOC contains one status Record with multiple status information.

- Status at each level is appended to IDOC. E.g. When IDOC is created in SAP, Status is “This IDoc has been generated through a test transaction”, When the IDOC is added to system it is “IDOC added”, “IDOC ready to be transferred to Application”……

- Status should always be read bottom-up. Status at the top is the latest status.

- Some Example of Status Records:

o Inbound:

 53 - IDOC successfully posted

 51 – IDOC Failed

 64 - IDOC ready to be transferred to Application

o Outbound:

 30 – IDOC ready for Dispatch

 03 – IDOC passed to port OK

 12 – IDOC Dispatched

 16 – Functional Acknowledgement Positive

17 – functional Acknowledgement Negative

Why is ALE used?

o Geographical Location

o Consolidation

o System Capacity

o Mission-Critical Applications

o Upgrading a module separately

o Data Security

o Business Reasons

ALE Setup:

o Document ALE-EDI Documentation talks about setup for both EDI and ALE. This document covers the setups specific to ALE.

o ALE is mainly used for transfer of Master or Transaction data within organization onto distributed servers. Hence the partner in most practical cases is Logical System.

o In case of ALE, 2 types of IDOCs are generated:

 Master IDOC: This IDOC is in memory and is not stored in the system. You cannot view a Master IDOC.

 Communication IDOC: From Master IDOC communication IDOCs are generated, one each for all the recipient system, considering the filters. If there are 3 recipient systems which can receive this IDOC, there would be one Master IDOC generated and 3 communication IDOCs.

o Steps in ALE Setup:

 Maintain Logical system

 Assign Logical system to Client

 Setup an RFC destination (SM59) (Name same as Logical System Name)

 Port Definition

 Maintain Customer Model (BD64)

 Generate Partner Profile (BD82)

 Distribute Customer Model (BD64)

o In ALE you partner is always a Logical system.

Reward points if it helpful

Regards,

Govind.

[Former Member]

Dear Ramana,

<b>BDC:</b>

http://help.sap.com/saphelp_erp2005/helpdata/en/fa/097119543b11d1898e0000e8322d00/frameset.htm

Batch Data Communication is used for mass upload of data in to SAP.

Steps:

1. Fetch Data (Download/Read Dataset/Select from Tables)

3. Massage data as per SAP format.

3. Validation Check

4. Pass valid data to BDC (Call Transaction/Session) or BAPI

5. In case of session method - session log is generated. In case of Call transaction you can use an internal table with structure BDCMSGCOLL to get messages. In case of BAPI the messages will be returned in return table (strcutre BAPIRET2/BAPIRETTAB).

<b>ALE and IDOC:</b>

ALE and IDOC:

ALE stands for Application Link Enabling and is used for distribution of data. IDOC is an Intermediate Document. It carries the application data from one server to another server.It uses the RFC(Remote Function call) .

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.

It is the the combination of Segements.

Segment : All the required fields will get assigned in relavant segement.Like that we will have lot of segments.We will assign all the segments to IDOC type.In the required level(Parent & child level .Like tree nodes).

Idocs Type is a Structure by lot of segments.

IDOC is generared at the time of run time .

It will have the data.

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.

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_off...

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

Hope this will help.

Regards,

Naveen.

[Former Member]

hi

<b>IDOC</b>

An Idoc is simply a data container that is used to exchange an information between 2 processes that can understand the syntax and semantics of the data.

in sap Idocs are stored in database tables

Idocs are independent of the sending and receiving system

Typically an Idoc contains

control records

<b>What is BDC?</b>

Batch Data Communication or BDC is a batch interfacing technique that SAP developed. It is mainly used for uploading data into the SAP R/3 system. BDC works by simulating the user input from transactional screen via an ABAP program.

The data input data file will come in the form of a flat file which the user save as file type txt file or prn file from the Microsoft Excel program. An Abaper will create a program to read the text file and upload into the SAP system.

Normally, the tcode SHDB will be used to record the transaction code the user used. After, the simulation, the Abaper can generate a sample program and modify from there. It makes the programming easier and faster.

data records

ststus records

<b>ALE</b>

Application Link Enabling

- Application Link Enabling (ALE) is a mechanism for the exchange of business data between loosely-coupled R/3 applications built by customers of SAP, the enterprise resource management program. ALE provides SAP customers with a program distribution model and technology that enables them to interconnect programs across various platforms and systems.

There are three layers in the ALE system: application services, distribution services, and communication services. The vehicle for data transfer is called an IDoc (intermediate document), which is a container for the application data to be transmitted. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model. The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system. If the data is distributed from a master system, the same transaction performed by the sender will be performed by the receiving system, using the information contained in the IDoc.

Changes made to fields in master data tables can be set to trigger distribution of the changes to slave systems, so that multiple database servers can update the same information simultaneously. IDocs carry information directly between SAP systems. In order to communicate with a non-SAP system, an IDoc is first transmitted to an intermediary system that translates the data to a format that will be understood by the receiver. Return data also passes through the translating system, where it is again encapsulated into an IDoc.

regards

[Former Member]

hhi

BAPI Step by step Guidance

BAPI stands for Business Application Programming Interface.

There are 5 different steps in BAPI.

- Create BAPI Structure

- Create BAPI Function Module or API Method.

- Create BAPI object

- Release BAPI Function Module.

- Release BAPI object.

Step1. Creating BAPI Structure:

- Go to <SE11>.

- Select Data Type & Enter a name.

- Click on Create.

- Note: Always BAPI should be in a development class with request number (Not Local Object).

- Select Structure & hit ENTER.

- Enter the fields from your database. Make sure that the first field is the Primary Key Field.

- Then SAVE & ACTIVATE.

Step 2. Creating BAPI module:

- Enter TR.CODE <SE37>.

- Before entering any thing, from the present screen that you are in, select the menu

Goto -> Function Groups -> Create Group.

Enter a name (Note: This name Must start with ZBAPI)

Let this screen be as it is and open another window and there, enter TR.CODE <SE80).

Click on the Third ICON that says Inactive Objects.

Select the group that you just created and click on Activate.

Notice that the group you created will disappear from the list of inactive objects.

- Go back to <SE37> screen and enter a name and hit <ENTER>. Then enter the group name that you just created and activated.

NOTE: When you release a function module the respective group will be attached to that particular application. It cannot be used for any other application. NEVER include an already existing group that is attached to another module.

Now click on the first Tab that says [ATTRIBUTES] and select the radio button that says remote-enabled module since we will be accessing this from any external system.

Then click on the second tab that says [IMPORT].

Enter a PARAMETER NAME, TYPE and the structure you created in the first step. Also select the check box &#8216;Pa&#8217;. All remotely enabled functional modules MUST be Pa enabled, where Pa means &#8216;Passed by Value&#8217; and if you don&#8217;t select &#8216;Pa&#8217;, then that means it will be passed by reference..

Then click on tab that says [EXPORT].

Enter the following as is in the first three fields

RETURN TYPE BAPIRETURN (These 3 field values are always same)

Here also select &#8216;Pa&#8217; meaning Pass by value.

Note: BAPIRETURN contains structure with message fields.

Then SAVE and ACTIVATE.

Step 3. Creating BAPI object:

- Enter Tr.Code <SWO1> (Note. It is letter &#8216;O&#8217; and not Zero).

- Enter a name and then click on create. Enter details.

NOTE: Make sure that that Object Type and Program name are SAME.

- Enter Application &#8216;M&#8217;, if you are using standard table Mara. If you are using your own database then select &#8216;Z&#8217; at the bottom.

- Then hit <ENTER>.

- Now we have to add &#8216;Methods&#8217;. High light METHODS and then select the following from the menu:

Goto Utilities -> API Methods -> Add Methods.

- Enter function Module name and hit <ENTER>.

- Select the second FORWARD ARROW button (>)to go to next step.

- Check if every thing looks ok and again click on FORWARD ARROW button (>).

- Then select &#8216;YES&#8217; and click on <SAVE>.

- Now on a different screen goto TR.CODE <SE37>. Enter Function Module name and select from the top menu Function Module -> Release -> Release.

- Goback to TR.CODE <SWO1>.

Here select the menu combination shown below in the same order.

- Edit -> Change Release Status -> Object Type Component -> To Implemented.

- Edit -> Change Release Status -> Object Type Component -> To Released.

- Edit -> Change Release Status -> Object Type -> To Implemented.

- Edit -> Change Release Status -> Object Type -> To Released.

- Then click on <SAVE>.

- Then click on Generate Button (4th button from left hand side looks like spinning wheel).

- Then Click on the button that says &#8216;PROGRAM&#8217; to see the source code.

To check if this is present in work flow goto TR.CODE <BAPI>.

Here it shows business object repository.

- First click on the middle button and then select &#8220;ALL&#8221; and hit ENTER.

- Goto tab [ALPHABETICAL] and look for the object that you created. This shows that the BAPI object has been created successfully.