Building Inbound IDoc
I am creating an inbound IDoc using ABAP. I have successfully created the IDoc, but I am getting errors, I believe because of the format of the Data Records in the IDoc. Here are the fields for the Data Records:
MANDT - using sy-mandt
DOCNUM
SEGNUM
SEGNAM - populating with segment name
PSGNUM
HLEVEL
DTINT2
SDATA - populating with data based on segment format
Can somebody either explain, or provide a link to instructions on how the other elements should be populated. I am getting a "flat" IDoc, and I think it's because I am not populating the hlevel, and possibly other elements, properly. I'm just not sure what to put in these elements to show the correct hierarchy of the IDoc.
Denise,
here is an example of updating contract prices using an ABAP, hope this helps
DATA: I_IDOC_DATA LIKE EDIDD OCCURS 0 WITH HEADER LINE,
I_IDOC_COMM LIKE EDIDC,
*--- Fills receiver tables
CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
IMPORTING
OWN_LOGICAL_SYSTEM = WA_LOGSYS
EXCEPTIONS
OWN_LOGICAL_SYSTEM_NOT_DEFINED = 1
OTHERS = 2.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*--- Create IDoc control-record
CLEAR I_IDOC_COMM.
I_IDOC_COMM-MESTYP = 'COND_A'.
I_IDOC_COMM-IDOCTP = 'COND_A01'.
I_IDOC_COMM-DIRECT = '2'.
I_IDOC_COMM-SERIAL = SY-DATUM.
I_IDOC_COMM-SERIAL+8 = SY-UZEIT.
I_IDOC_COMM-RCVPOR = SPACE.
I_IDOC_COMM-RCVPRT = 'LS'.
I_IDOC_COMM-RCVPRN = WA_LOGSYS.
I_IDOC_COMM-SNDPOR = P_SNDPOR.
I_IDOC_COMM-SNDPRT = 'LS'.
I_IDOC_COMM-SNDPRN = WA_LOGSYS.
LOOP AT I_COND_UPD INTO WA_COND_UPD.
REFRESH I_IDOC_DATA.
*--- Fill E1KOMG segment
CLEAR E1KOMG.
E1KOMG-KVEWE = 'A'.
E1KOMG-KOTABNR = WA_COND_UPD-KOTABNR.
E1KOMG-KAPPL = WA_COND_UPD-KAPPL.
E1KOMG-KSCHL = WA_COND_UPD-KSCHL.
IF WA_COND_UPD-KOTABNR = '017'.
MOVE: WA_COND_UPD-LIFNR TO E1KOMG-VAKEY+0(10).
MOVE: WA_COND_UPD-MATNR TO E1KOMG-VAKEY+10(18).
MOVE: WA_COND_UPD-EKORG TO E1KOMG-VAKEY+28(4).
MOVE: WA_COND_UPD-WERKS TO E1KOMG-VAKEY+32(4).
MOVE: WA_COND_UPD-ESOKZ TO E1KOMG-VAKEY+36(1).
IF E1KOMG-VAKEY+36(1) = SPACE.
MOVE '0' TO E1KOMG-VAKEY+36(1).
ENDIF.
ENDIF.
CLEAR I_IDOC_DATA.
MOVE 'E1KOMG' TO I_IDOC_DATA-SEGNAM.
MOVE E1KOMG TO I_IDOC_DATA-SDATA.
APPEND I_IDOC_DATA.
*--- Fill E1KONH segment
CLEAR E1KONH.
E1KONH-DATAB = WA_COND_UPD-DATAB.
E1KONH-DATBI = WA_COND_UPD-DATBI.
CLEAR I_IDOC_DATA.
MOVE 'E1KONH' TO I_IDOC_DATA-SEGNAM.
MOVE E1KONH TO I_IDOC_DATA-SDATA.
APPEND I_IDOC_DATA.
*--- Fill E1KONP segment
CLEAR E1KONP.
E1KONP-KSCHL = WA_COND_UPD-KSCHL.
E1KONP-STFKZ = WA_COND_UPD-STFKZ.
E1KONP-KZBZG = WA_COND_UPD-KZBZG.
E1KONP-KSTBM = WA_COND_UPD-KSTBM.
e1konp-konms = wa_cond_upd-konms.
PERFORM CONVERT_ISO_UNIT USING WA_COND_UPD-KONMS
CHANGING E1KONP-KONMS.
E1KONP-KSTBW = WA_COND_UPD-KSTBW.
E1KONP-KONWS = WA_COND_UPD-KONWS.
E1KONP-KRECH = WA_COND_UPD-KRECH.
E1KONP-KBETR = WA_COND_UPD-KBETR.
E1KONP-KONWA = WA_COND_UPD-KONWA.
E1KONP-KPEIN = WA_COND_UPD-KPEIN.
e1konp-kmein = wa_cond_upd-kmein.
PERFORM CONVERT_ISO_UNIT USING WA_COND_UPD-KMEIN
CHANGING E1KONP-KMEIN.
E1KONP-PRSCH = WA_COND_UPD-PRSCH.
E1KONP-KUMZA = WA_COND_UPD-KUMZA.
E1KONP-KUMNE = WA_COND_UPD-KUMNE.
e1konp-meins = wa_cond_upd-meins.
PERFORM CONVERT_ISO_UNIT USING WA_COND_UPD-MEINS
CHANGING E1KONP-MEINS.
E1KONP-KZNEP = WA_COND_UPD-KZNEP.
E1KONP-ZAEHK_IND = WA_COND_UPD-ZAEHK_IND.
CLEAR I_IDOC_DATA.
MOVE 'E1KONP' TO I_IDOC_DATA-SEGNAM.
MOVE E1KONP TO I_IDOC_DATA-SDATA.
APPEND I_IDOC_DATA.
ENDLOOP.
CALL FUNCTION 'IDOC_WRITE_AND_START_INBOUND'
EXPORTING
I_EDIDC = I_IDOC_COMM
DO_COMMIT = 'X'
IMPORTING
DOCNUM = WA_DOCNUM
ERROR_BEFORE_CALL_APPLICATION =
TABLES
I_EDIDD = I_IDOC_DATA
EXCEPTIONS
IDOC_NOT_SAVED = 1
OTHERS = 2
Similar Messages
-
Creation of Inbound Idoc for the Outbound Idoc in same client
Hi,
My requirement:
Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
I found there is a field for function module in WE21,can this be used to get the requirement done.
Please suggest.
Regards,
AmarExample of a program that create and post an inbound idoc....maybe that will help you:
report zzinbound_idoc.
data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
data: g_edidd like edi_dd40 occurs 0 with header line.
data: g_e1bpache09 like e1bpache09.
parameter: mode type c default 'A'.
refresh: g_idoc_control_record, g_edidd.
clear: g_idoc_control_record, g_edidd.
*-Build Control Record -*
g_idoc_control_record-mestyp = 'ACC_DOCUMENT'. "Message type
g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
g_idoc_control_record-direct = '2'. "Direction
* Receiver
case sy-sysid.
when 'DE2'.
g_idoc_control_record-rcvpor = 'SAPDE2'. "Port
g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-rcvprt = 'LS'. "Partner type
g_idoc_control_record-rcvpfc = ''. "Partner function
* Sender
g_idoc_control_record-sndpor = 'A000000002'. "tRFC Port
case sy-sysid.
when 'DE2'.
g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
endcase.
g_idoc_control_record-sndprt = 'LS'. "Partner type
g_idoc_control_record-sndpfc = ''. "Partner function
g_idoc_control_record-refmes = 'Customer clearing'.
append g_idoc_control_record.
*-Build Idoc Segments -*
*---E1KOMG
clear g_edidd.
clear g_e1bpache09.
g_edidd-segnam = 'E1BPACHE09'.
g_edidd-segnum = 1.
move g_e1bpache09 to g_edidd-sdata.
append g_edidd.
*-Create idoc -*
*-Syncronous
if mode = 'S'.
call function 'IDOC_INBOUND_SINGLE'
exporting
pi_idoc_control_rec_40 = g_idoc_control_record
* PI_DO_COMMIT = 'X'
* IMPORTING
* PE_IDOC_NUMBER =
* PE_ERROR_PRIOR_TO_APPLICATION =
tables
pt_idoc_data_records_40 = g_edidd
exceptions
idoc_not_saved = 1
others = 2.
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
endif.
*-Asynchronus
else.
call function 'IDOC_INBOUND_ASYNCHRONOUS'
in background task as separate unit
tables
idoc_control_rec_40 = g_idoc_control_record
idoc_data_rec_40 = g_edidd.
commit work.
endif.
write: / 'Well done!'. -
Inbound IDOC Format (Flat File)
Hi,
I'm using SAP CRM Middleware for communication between CRM and Legacy System.
I have configured Outbound IDOCs and I see something like this:
EDI_DC40 2200000000000000023700 3012 CRMXIF_PARTNER_SAVE_M01 CRMXIF_PARTNER_SAVE_M
E201CRMXIF_PARTNER_COMPLEX000 220000000000000002300000100000001CRMXIF_PARTNER_COMPLEX
E201CRMXIF_PARTNER_HEADER000 220000000000000002300000200000102CRMXIF_PARTNER_HEADER BusinessPartner U
E201CRMXIF_PARTNER_KEYS000 220000000000000002300000300000203CRMXIF_PARTNER_KEYS 0000000014488DDB8AD891249EE10080010A6CA883
The questions are:
I need to know how do the following information must be filled in an Inbound IDOC:
The first characters I understand that corresponds to the Structure name, IDOC Number, IDOC Line...
So I need how do fields like IDOC number must be filled in an Inbound IDOC
Thanx in advance..
BTW. I'm expecting IDOCs as flat files so I need to explain to the Legacy Technician how to fill this fields.Hi,
Go to transaction WE30 and give the IDoc basictype name CRMXIF_PARTNER_REL_SAVE_M01 and press the view-button (or press F7 key).
This information you will need.
The records are builded using the following structure:
1st record contains control record information and follows the structure of table EDIDC.
Starting at where "220" is given (this is the CLIENT), it is followed by the IDoc number field DOCNUM (16 digits) and so on. Not all fields must be filled, only those that are used for inbound messaging. Keep here in mind: Less fields filled will probably work better (because SAP will add its own details on arrival of the IDoc).
All following records follow the structure of table EDID4 upto the field: HLEVEL (Hierarchy level, identical to the level found in WE30).
Thereafter it is followed by the name of the segment (including spaces) and after this it will follow the exact structure of the segment.
To view a sample, just generate a dummy (test) IDoc and use transaction WE19 to fill in the fields after changing to the correct IDoc type.
Hope this helps you out.
Regards,
Rob. -
Inbound Idoc customer number conversion
I am new to EDI and have a question to ask you both about inbound IDOC's. We have customers sending remittance advices through EDI. The customer numbers in them are their own customer numbers. In SAP, we maintain different customer numbers. Where do the mapping of the customer numbers take place -- In the EDI subsytem itself or in SAP? If in SAP, can you let me know the procedure to do this.
Any help will be appreciated and points awarded.
Thanks,
Nile.Hey Fren,
1. Data Mapping
Within the framework of SAP EDI, the conversion of a business document in IDoc format to an EDI standard format (and vice versa) is the most important task performed by a subsystem. This process is resource intensive and, hence, is better done at the subsystem level than within SAP. The following conversions and translations are carried out by the subsystem.
Creating a control record for each inbound IDoc.
An inbound IDoc must have a control record. The EDI subsystem builds the control record using the information stored in its local repository or from the SAP repository.
Removing the control record during the outbound process.
The control record in the IDoc file is used by the subsystem for housekeeping functions, such as locating the trading partner profile. The data on the control record is not needed for translating the content of the EDI documents.
Translating data from IDoc format to EDI format.
For an outbound transaction, the EDI subsystem converts data in the IDoc format to a suitable EDI format.
Translating data from EDI format to IDoc format.
For an inbound transaction, the EDI subsystem converts data in the standard EDI format to IDoc format.
Bundling and unbundling IDocs.
If several IDocs are passed to the EDI subsystem in one file, the subsystem separates them into individual documents. Similarly, on the inbound process the subsystem can bundle multiple IDocs into a single file to improve performance.
2 Maintaining the Partner Profile
A partner is defined as the business partner with whom you conduct business and exchange EDI documents. These partners are not necessarily the same as the partners in the partner profile of SAP. However, the concept is quite similar. In SAP, the partner profile maintains parameters specific to the IDoc process, and in the subsystem the partner profile maintains parameters specific to the EDI process. Some typical attributes in a partner profile are
· A unique partner number
· The partner type (Customer, Vendor)
· The standard used (EDIFACT, ANSI X12, and so on)
· The version of the EDI standard
· The EDI message exchanged (850, 860, ORDERS, ORDCHG)
· A functional acknowledgment flag
3 Triggering the Inbound Process
After receiving an inbound EDI transmission and creating an IDoc file, the subsystem is often responsible for triggering the inbound process. SAP provides a program named startrfc to start any RFC−enabled function module from the operating system level. For the EDI process, the subsystem uses the startrfc program to
trigger the function module EDI_DATA_INCOMING. Chapter 6, "Configuring Basic EDI Components," provides the complete details and parameters of the startrfc progam.
4 Reporting Process Status to SAP
In an outbound process, after an IDoc has been transferred from SAP to the subsystem, SAP loses control over the process. However, SAP maintains visibility into the process by requiring the subsystem to report on the status of the process. SAP provides a file interface for the subsystem to send a status report at every milestone.
I hope you got some idea from this process.....
<REMOVED BY MODERATOR>
Warm Regards,
Abhi...
Edited by: Alvaro Tejada Galindo on Apr 25, 2008 4:36 PM -
Need Code to generate Inbound Idocs
Hi friends
i have a flat file consists of delivery confirmation data
by using this i need to generate inbound idocs
i filled all the segments in idoc type /afs/delvry03 and message type whscon
can any one have the code to generate inbound idocs
please remember that here i am not using XI
thanks
AnilHi this is for Stand alone Programs, I hope it is useful to you.
Program Flow
The program logic contains the following blocks:
1. Provide a selection screen to allow a user to specify the various objects for which IDocs are to be generated.
2. Determine the key of the application document from the object specified in step 1.
3. Select application data from the database using the object key identified in step 2.
4. Populate control record information.
5. Populate an internal table of type EDIDD with data records for the various segments.
6. Call the ALE service layer (MASTER_IDOC_DISTRIBUTE) to create the IDocs in the database.
7. Commit work.
The program in Listing 32-2 generates the monthly report IDoc ZMREPT01, which illustrates a stand-alone outbound process.
Listing 32-2
REPORT ZARNEDI1 MESSAGE-ID ZE.
Parameters
object key (Social security number for the employee)
PARAMETERS: P_SSN LIKE ZEMPDETAIL-SSN.
message type
PARAMETERS: P_MESTYP LIKE EDMSG-MSGTYP OBLIGATORY.
destination system
PARAMETERS: P_LOGSYS LIKE TBDLST-LOGSYS.
Constants
DATA:
segment names
C_HEADER_SEGMENT LIKE EDIDD-SEGNAM VALUE 'Z1EMHDR',
C_WEEKLY_DETAILS_SEGMENT LIKE EDIDD-SEGNAM VALUE 'Z1WKDET',
C_CLIENT_DETAILS_SEGMENT LIKE EDIDD-SEGNAM VALUE 'Z1CLDET',
C_SUMMARY_SEGMENT LIKE EDIDD-SEGNAM VALUE 'Z1SUMRY',
idoc type
C_MONTHLY_REPORT_IDOC_TYPE LIKE EDIDC-IDOCTP VALUE 'ZMREPT01'.
Data declarations
idoc control record
data: control_record_out like edidc.
employee header data
DATA: FS_EMPHDR_DATA LIKE Z1EMHDR.
employee weekly details data
DATA: FS_WEEKDET_DATA LIKE Z1WKDET.
client details data
DATA: FS_CLIENTDET_DATA LIKE Z1CLDET.
employee monthly summary data
DATA: FS_SUMMARY_DATA LIKE Z1SUMRY.
total hours and amount for the summary segment
DATA: TOTAL_HRS_MONTH TYPE I,
TOTAL_AMT_MONTH TYPE I.
Database Tables
Application data tables
TABLES: ZEMPDETAIL, ZEMPWKDET.
Internal tables
DATA:
weekly details - appplication data
IT_WKDET LIKE ZEMPWKDET OCCURS 0 WITH HEADER LINE,
data records
INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE,
communication idocs geneerated
IT_COMM_IDOCS LIKE EDIDC OCCURS 0 WITH HEADER LINE.
Program logic
********************Select Application Data***************************
SELECT SINGLE * FROM ZEMPDETAIL WHERE SSN = P_SSN.
IF SY-SUBRC NE 0.
MESSAGE E001 WITH P_SSN.
EXIT.
ENDIF.
SELECT * FROM ZEMPWKDET INTO TABLE IT_WKDET WHERE SSN = P_SSN.
IF SY-SUBRC NE 0.
MESSAGE E002 WITH P_SSN.
EXIT.
ENDIF.
********************Build Control Record******************************
Fill control record information
CONTROL_RECORD_OUT-MESTYP = P_MESTYP.
control_record_out-idoctp = c_monthly_report_idoc_type.
control_record_out-rcvprt = 'LS'.
control_record_out-rcvprn = p_logsys.
********************Build Data Records********************************
*--Employee header--
fill the employee header information
FS_EMPHDR_DATA-LNAME = ZEMPDETAIL-LNAME.
FS_EMPHDR_DATA-FNAME = ZEMPDETAIL-FNAME.
FS_EMPHDR_DATA-SSN = ZEMPDETAIL-SSN.
FS_EMPHDR_DATA-DOB = ZEMPDETAIL-DOB.
fill the administrative section of the data record
INT_EDIDD-SEGNAM = C_HEADER_SEGMENT.
INT_EDIDD-SDATA = FS_EMPHDR_DATA.
append the employee header data record to the IDoc data
APPEND INT_EDIDD.
*--Employee weekly details--
LOOP AT IT_WKDET.
fill the weekly details for each week
FS_WEEKDET_DATA-WEEKNO = IT_WKDET-WEEKNO.
FS_WEEKDET_DATA-TOTHOURS = IT_WKDET-TOTHOURS.
FS_WEEKDET_DATA-HRLYRATE = IT_WKDET-HRLYRATE.
add administrative information to the data record
INT_EDIDD-SEGNAM = C_WEEKLY_DETAILS_SEGMENT.
INT_EDIDD-SDATA = FS_WEEKDET_DATA.
append the data for the week to the IDoc data
APPEND INT_EDIDD.
Client details of each week
FS_CLIENTDET_DATA-CLSITE = IT_WKDET-CLSITE.
FS_CLIENTDET_DATA-WORKDESC = IT_WKDET-WORKDESC.
add administrative information to the data record
INT_EDIDD-SEGNAM = C_CLIENT_DETAILS_SEGMENT.
INT_EDIDD-SDATA = FS_CLIENTDET_DATA.
append the client details for the week to the IDoc data
APPEND INT_EDIDD.
ENDLOOP.
*--Employee monthly summary--
compute total hours and amount for the month
LOOP AT IT_WKDET.
TOTAL_HRS_MONTH = TOTAL_HRS_MONTH + IT_WKDET-TOTHOURS.
TOTAL_AMT_MONTH = TOTAL_AMT_MONTH + ( IT_WKDET-TOTHOURS *
IT_WKDET-HRLYRATE ).
ENDLOOP.
fill the summary information
FS_SUMMARY_DATA-TOTHRS = TOTAL_HRS_MONTH.
FS_SUMMARY_DATA-TOTAMT = TOTAL_AMT_MONTH.
condense the summary record fields to remove spaces
CONDENSE FS_SUMMARY_DATA-TOTHRS.
CONDENSE FS_SUMMARY_DATA-TOTAMT.
add administrative information to the data record
INT_EDIDD-SEGNAM = C_SUMMARY_SEGMENT.
INT_EDIDD-SDATA = FS_SUMMARY_DATA.
append summary data to the IDoc data
APPEND INT_EDIDD.
*************Pass control to the ALE layer****************************
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
master_idoc_control = control_record_out
TABLES
COMMUNICATION_IDOC_CONTROL = IT_COMM_IDOCS
MASTER_IDOC_DATA = INT_EDIDD
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
IF SY-SUBRC NE 0.
MESSAGE E003 WITH P_SSN.
ELSE.
LOOP AT IT_COMM_IDOCS.
WRITE: / 'IDoc generated', IT_COMM_IDOCS-DOCNUM.
ENDLOOP.
COMMIT WORK.
ENDIF. -
Hi,
iam working on an inbound IDOC TPSSHT01, i need to add an extrta field and segment , so i create an data element and Z segment and add the field in the segment
i have to copy the TPSSHT01 to a ZTPSSHT01 and do the IDoc extension ,
i have to copy the function module IDOC_INPUT_SHIPPL to Z_IDOC_INPUT_SHIPPL
Can any body let me know what are the steps that i have to follow to process the inbound idoc with the above requirment
Cheers,
SaiHi ,
Follow this procedure .
In bound Idoc
Step 1: Create segment
a. T.code WE31
b. Enter a new segment type and press create button
c. Give a short text
d. Enter the field names say FIELD NAME : MATNR ;; DATA ELEMENT: CHAR(18)
e. Save the segment (zkrishseg)
Step 2: Create IDOC type
a. T.code WE30
b. Enter a new IDOC type name
c. Choose the basic type and press the create button.
d. Choose the create new option button and enter a description and press enter
e. Place the cursor on the type name and then press create button.
f. Enter the segment name created in step 1 and check the mandatory segment check box
g. Enter minimum number and maximum number as 1 and press enter.
h. Then save the IDOC type. (zkrishtyp)
Step 3: Create message type
a. T.code WE81
b. Press change button.
c. Press new entries button.
d. Enter a message type and short text and press save button. (zkrishmsg)
Step 4: Assign message type to IDOC type.
a. T.code WE82
b. Press change button
c. Press new entries button.
d. Enter the created message type, IDOC type and version release (46B or 46C)
Step 5: Create a function module for inbound. (Z_IDOC_KRISH_INBOUND)
Step 5A: Create characteristics of inbound FM.
a. T.code BD51
b. Click New entries
c. Enter the IDOC function module name and 1(individual type) in input t..
d. Save it.
Step 6: Assignment of FM to log, message and type.
a. T.code WE57
b. Go for change mode and click new entries.
c. In processing by enter FM name and enter F as type.
d. Enter basic type (idoc type-zkrishtyp) and message type (zkrishmsg) in the respective text boxes.
e. Choose the direction as 2 Inbound.
f. Save the data.
Step 7. : Creation of inbound process code.
a. T.code WE42
b. Go to change mode and click create entries.
c. Enter a new process code and description (zidockrish)
d. Enter the FM name in the identification text box
e. Choose processing with ALE service
f. Choose processing by FM and click Save button
g. In the next screen, select the FM name and click save button
Step 7a : Creation of inbound process code.
h. T.code SM59
i. Select R/3 connection and click create.
j. Enter all system related things(for Eg. Connection type as 3, Target host as SAP04,
Description , and Logon details and save.
Step 8: Define a port
a. T.code WE21
b. Click on Transactional RFC and press the Create button
c. Enter a port name and description. (ztestkrish)
d. Choose the release type.
e. Choose the RFC destination.
f. To create RFC destination go to SPRO and search RFC destination and create.
g. Save the data.
Step 9. Define logical system
a. T.code SALE
b. Click down the sending and receiving systems
c. Click down the logical systems
d. Choose Define logical system.
e. Go for new entries.
f. Enter a new name and description and save it. (zkrishlog)
Step 10. Create partner profile
a. T.code WE20
b. Choose partner type LS and click create.
c. Enter the logical system name in partner number
d. Then Save . Here Type is US.
e. click + icon(create inbound parameter) in the bottom. Note: Two table control subscreens will appear. One for inbound and the other for outbound. Click + icon in inbound area.
f. Enter the message type, process code and save the data.
Step 11. Checking the Idoc
a. T.code WE19,
b. Choose radio Basic type , enter the type name(zkrishtyp) and press execute button.
c. Click on EDIDC Number.
d. Enter partner Number, Partner type, Port Number for sender and recipient ( data remains same here for sender and recipient)
e. Enter Message type and press ENTER.
f. Click on empty space corresponding to SEGMENT name and enter Paarameters like MATNR, WERKS and CHARG etc .
g. Click standard inbound properties here and press enter see the result .
h. T.code WE02
i. Enter IDOC number press ENTER see the status.
Function Module in Inbound
Import Parameters
INPUT_METHOD LIKE BDWFAP_PAR-INPU Inbound method for the IDoc inb
MASS_PROCESSING LIKE BDWFAP_PAR-MASS Flag: Mass processing
Export Parameters
WORKFLOW_RESULT LIKE BDWF_PARAM-RESULT Final value of method
APPLICATION_VARIABLELIKE BDWF_PARAM-APPL_VAR Variable to be used by
IN_UPDATE_TASK LIKE BDWFAP_PAR-UPDATETASK Flag: Application has
CALL_TRANSACTION_DONLIKE BDWFAP_PAR-CALLTRANS Flag: Application
tables
IDOC_CONTRL LIKE EDIDC Control record (IDoc)
IDOC_DATA LIKE EDIDD Data record (IDoc)
IDOC_STATUS LIKE BDIDOCSTAT ALE IDoc status (subset of al
RETURN_VARIABLES LIKE BDWFRETVAR Assignment of IDoc or documen
SERIALIZATION_INFO LIKE BDI_SER Serialization objects for one
Source code
FUNCTION ZASHOKMODULE.
""Local interface:
*" IMPORTING
*" VALUE(INPUT_METHOD) LIKE BDWFAP_PAR-INPUTMETHD
*" VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*" VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT
*" VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR
*" VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*" VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*" IDOC_CONTRL STRUCTURE EDIDC
*" IDOC_DATA STRUCTURE EDIDD
*" IDOC_STATUS STRUCTURE BDIDOCSTAT
*" RETURN_VARIABLES STRUCTURE BDWFRETVAR
*" SERIALIZATION_INFO STRUCTURE BDI_SER
data: begin of w_data occurs 0.
include structure edidd.
data: end of w_data.
data: wa_data like ZASH1.
data : i_data like standard table of wa_data initial size 0.
*tables : zhemal1.
data : begin of wa_zhemal1.
include structure zhemal1.
data : end of wa_zhemal1.
data : i_ZHEMal1 like standard table of wa_ZHEMal1 initial size 0.
read table idoc_data with key SEGNAM = 'ZASH1'.
loop at IDOC_DATA into W_DATA where segnam = 'ZASH1'.
WA_DATA = W_DATA-SDATA.
wa_data = w_data-sdata.
append wa_data to i_data.
endloop.
MOVE IDOC_DATA-DOCNUM TO IDOC_STATUS-DOCNUM.
IDOC_STATUS-MSGID = 'ZABC'.
IDOC_STATUS-STATUS = 53.
IDOC_STATUS-MSGTY = 'S'.
IDOC_STATUS-MSGNO = '001'.
APPEND IDOC_STATUS.
LOOP AT i_data into wa_data.
wa_ZHEMal1-VBELN = wa_data-VBELN.
wa_ZHEMal1-POSNR = wa_data-POSNR.
wa_ZHEMal1-MATNR = wa_data-MATNR.
wa_ZHEMal1-MATWA = wa_data-MATWA.
wa_ZHEMal1-MATKL = wa_data-MATKL.
append wa_ZHEMal1 to i_ZHEMal1.
insert ZHEMal1 from table i_ZHEMal1 accepting duplicate keys .
ENDLOOP.
ENDFUNCTION.
For Out bond Steps are
1. Create segment
2. Create Type
3. Create Message Type
4. Assign message Type to Idoc Type.
5. Create Port
6. Define Logical systems.
7. Define Partner profile.
8. Create a Report program.
Report program Out bond
REPORT ZASH1 .
Outbound standalone idoc creation *
Program Name : Y_VENMAST_OUTBOUND_STANDALONE *
Description : Outbound standalone idoc creation for training *
to Unilever offshore team members *
Created by : Satyam Computer Services Ltd. *
Created on : 04.01.2002 *
Modification Log *
Developer Date Transport # Details *
Subramony 04.01.2002 *
Tables Declaration *
TABLES : zhemal1.
Internal table declaration *
data : i_zhem1 Like standard table of zhem1 with header line.
data : control_record_out like edidc.
*data: p type p decimals 2,
c(10) type c.
start-of-selection.
p = '3.14'.
c = p.
overlay c with '0000000000000'.
write c.
DATA : BEGIN OF I_EDIDD OCCURS 0.
INCLUDE STRUCTURE EDIDD.
DATA : END OF I_EDIDD.
DATA : BEGIN OF I_EDIDC OCCURS 0.
INCLUDE STRUCTURE EDIDC.
DATA : END OF I_EDIDC.
DATA : BEGIN OF I_zhemal1 OCCURS 0,
VBELN LIKE zhemal1-VBELN,
POSNR LIKE zhemal1-POSNR,
MATNR LIKE zhemal1-MATNR,
MATWA LIKE zhemal1-MATWA,
MATKL LIKE zhemal1-MATKL,
END OF I_zhemal1.
SELECT-OPTIONS : S_vbeln FOR zhemal1-vbeln .
START-OF-SELECTION.
PERFORM F_GET_zhemal1.
END-OF-SELECTION.
Building Control record
CONTROL_RECORD_OUT-MESTYP = 'ZASH1'.
CONTROL_RECORD_OUT-IDOCTP = 'ZASH1'.
CONTROL_RECORD_OUT-RCVPRT = 'LS'.
CONTROL_RECORD_OUT-RCVPRN = 'ZASH1'.
CONTROL_RECORD_OUT-sndPRT = 'LS'.
CONTROL_RECORD_OUT-sndPRN = 'ZASH1'.
PERFORM F_PROCESS_OUTPUT.
*PERFORM F_FILL_EDIDD.
PERFORM F_CREATE_IDOC.
Form F_GET_Y1COTU110 *
FORM F_GET_zhemal1.
SELECT VBELN POSNR MATNR MATWA MATKL
FROM ZHEMAL1
INTO TABLE I_ZHEMAL1
WHERE VBELN IN S_VBELN.
ENDFORM. " F_GET_zhemal1
Form f_process_output *
FORM F_PROCESS_OUTPUT.
LOOP AT I_zhemal1.
I_zhem1-VBELN = I_zhemal1-VBELN.
I_zhem1-POSNR = I_zhemal1-POSNR.
I_zhem1-MATNR = I_zhemal1-MATNR.
I_zhem1-MATWA = I_zhemal1-MATWA.
I_zhem1-MATKL = I_zhemal1-MATKL.
i_edidd-segnam = 'ZASH1'.
i_edidd-sdata = I_zhem1.
append i_edidd.
clear i_edidd.
ENDLOOP.
ENDFORM. " f_process_output
Form f_create_edidc *
FORM F_CREATE_IDOC.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
EXPORTING
MASTER_IDOC_CONTROL = CONTROL_RECORD_OUT
TABLES
COMMUNICATION_IDOC_CONTROL = I_EDIDC
MASTER_IDOC_DATA = I_EDIDD
EXCEPTIONS
ERROR_IN_IDOC_CONTROL = 1
ERROR_WRITING_IDOC_STATUS = 2
ERROR_IN_IDOC_DATA = 3
SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
OTHERS = 5.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
LOOP AT I_EDIDC.
WRITE :/ 'IDoc Generated :' , I_EDIDC-DOCNUM.
ENDLOOP.
COMMIT WORK.
ENDIF.
ENDFORM. " f_create_idoc
Please reward if useful. -
Good morning.
Please help me.
I must set up multiple inbound IDOCS, one of them is:
Type base : orders05.
message type : orders.
The process is : data is received xi / pi, and IDOCs must be created to fill the data transaction VA01 and VA02.
I have read many tutorials but I have not been clear what to do if we use a standard IDOC type base as ORDERS05.
what should I set in r / 3?
Thanks!!!Detailed ALE configuration as follows... This might be helpful to check both your PI and ECC or R/3.
1. First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
2. Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 Optional Step. Not mandatory
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
3. To Enable Acknowledgement:
SXMB_ADM ->Integration Engine Configuration ->Specific Configuration ->Add New entry -> Select parameters as:
Category: RUNTIME
Parameters: ACK_SYSTEM_FAILURE
Current Value: 1
4. GO TO SLD:
Create Technical System: Choose WEB AS ABAP if the system is R/3 -> Define SAP SID, Installation Number and Database Host Name a Maintain message Server Details according to Sender System -> Maintain Client Details of Sender System ->Select a Installed Product for Sender System
Create Business System: Choose WEB AS ABAP if the system is R/3 -> Choose the Technical System and the client Created Before -> Choose the Installed Product -> Set:
Business System Role: Application System
Related Integration Server: Integration Server
5. IDOC Tunneling in XI
To prevent performance consuming XMLization and de-XMLization IDOCs are tunneled through SAP XI IDOC adapter meaning no XMLiziation is executed before the IDOC is passed onto the pipeline. Note the message is converted to UTF-8 codepage.
6. Start transaction SXMB_ADM on SAP XI.
Select option Configuration->Integration Engine Configuration and add two parameters EXTERNAL_MAPPER in the category IDOC.
Configure the parameter according to the conditions below:
If Message Code and Message Function are specified in the partner profile:
<Snd.Syst.Id>.<Snd.Syst.Client>.ReceiverPort.<Mess.Type>.<Mess.Code>.<Mess.Function>
If only the Message Code is specified in the partner profile:
<Snd. System Id>.<Snd. System Client>.ReceiverPort.<Mess. Type>.<Mess. Code>
If only Message Function is specified in the partner profile:
<Snd.Syst.Id>.<Snd.Syst.Client>.ReceiverPort.<Mess.Type>..<Mess.Function>
7. Integration Builder Integration Directory:
Add Business System: Adapter Specific Identifiers -> 'Logical System' identical to the 'Logical System Name' in the SLD Business System
IDoc Receiver Communication Channel: port the same as XI System IDX1 -
How to post inbound idoc in sap system?
Dear All,
How to post inbound Idoc in sap system?
Regards,
Amar
Edited by: amar kumar on Nov 23, 2009 2:53 PMHi Amar,
Use the FM IDOC_WRITE_AND_START_INBOUND to post an inbound IDoc. Just build the EDIDD and *EDIDC8 tables and enter a profile for a inbound message type from a partner. It returns a IDoc number. Don't forget to do commit work.
Regards
Abhii -
Creation of Sales Order and Service Contract from Inbound IDOC
Hi Experts,
My requirement is to create a Sales Order as well as a Service Contract from one Inbound IDOC. I am getting the Inbound IDOC from a third Party. The message type is ORDERS and Basic Type is ORDERS02. How ever i am using an extension type IDOC which carries all the required data for Sales Order and Service Contract. My requirement is like, to create a Sales Order first.
I have created a Z FM which is attached to the Process Code and subsequently to the message type. Inside the FM i an calling FM 'IDOC_INPUT_ORDERS' for creation of Sales Order. After that i am changing the IDOC data for the Document Type. I am changing the document type which is responsible for Contract Creation.
Then I am again calling the FM 'IDOC_INPUT_ORDERS' for creation of Contract with the help of IDOC data. But here the Contract is not getting created. It's getting failed during the Batch input session.
I need to solve this problem as soon as possible. Please help me. If there are any other options also please share.
Thanks in Advance.
Regards,
PriyabrataActually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata -
Creation of Service Contract from Inbound IDOC
Hi Experts,
I am using Inbound IDOC type ORDERS02 with message type ORDERS for creation of Sales Order. Now my requirement is like to create a Service Contract from that Inbound IDOC. The IDOC type contains all the data require to create a Service Contract. The scenario is like, after creation of Sales Order it will check for the corresponding Service Contract exits or not by querying on a Z table which contains all those entries.
So my idea is to create a Z Program, in which it will check for the Service Contract and will create the same by reprocessing the same IDOC or by calling some Function Module. Please suggest how shall i proceed to create a Service Contract.
Is there any way to reprocess the IDOC or to collect the Data from the IDOC segments pass them to a FM which is responsible for creation of Inbound IDOC. Please suggest if this is feasible.
Thanks in Advance.
Regards,
Priyabrata.Actually there is problem with BDCDATA. Inside the FM it's calling transaction with help of BDCDATA. If i am creating a Sales order or contract alone its creating successfully. But when i am trying to create both, it's retuning sy-subrc '1001' after calling the transaction on the second attempt. Is there any problem with BDCDATA like we can't handle with less time gap? Please help and give your inputs.
Regards,
Priyabrata -
How to read file from prsntn server in Inbound idoc FM.
Hi Experts,
I am new to idoc.
I have requirment that i need to read a file from presentation and application server and put in inbound idoc FM.Idoc will be processed in batch.
How can i put selection screen in FM and read the file?or how can i proceed with the solution?
Please help..
UmeshHi Umesh,
My understanding on your requirement is to read a file from pres. server and pass the data to an IDoc function module. Am I correct?
If this is the case then you can create a report which picks up the file from pres. server and then read data from the file and pass it to the parameters of the required function module.
Hope this helps.
Regards,
-Sandeep -
How to create the INBOUND Function Module for INBOUND IDOCs
Hi Friends,
Can any Suggest me How to proceed to Create an INBOUND Function Module for Processing the INBOUND IDOCS
which are recieved from XI Server ?
I am working in SAP-ISU
Here i will recieve the INBOUND IDOCs for the Meter Reading Orders.
We have a Standard INBOUND FUNCTION MODULE
IDOC_INPUT_ISU_MR_UPLOAD
which Uploads the Meter Reading Results.
I copied the Same function Module into ZIDOC_INPUT_
and working on it.
Can any one suggest me, whether i am going in correct way or not.
In IDOC_INPUT_ISU_MR_UPLOAD Inbound fun module,
BAPI_MTRREADDOC_UPLOAD is used to Update or Insert the Meter Reading Results,
My requirment is to Insert and Update the Meter Reading Orders which are Inbounded from XI.
Can I Use the Same BAPI
BAPI_MTRREADDOC_UPLOAD
to Update the below fields,
EABL-SERNR
EABL-ZWNUMMER
EABLG-ABLESGR
EABL-V_ZWSTAND
EABL-N_ZWSTAND
EABL-ABLHINW
EABL-ZSKIPC
EABL-ADAT
EABL-ATIMTATS
EABL-ADATTATS
EABL-ATIM
EABL-ZMESSAGE
EABL-ABLESER(Meter reader number)
Kindly Suggest me,
Thanks in Advance,
GaneshHello Ganesh
I think you are going completely astray with you z-function module for IDoc processing.
If you look at TABLES parameter METERREADINGRESULTS (type BAPIEABLU ) of BAPI_MTRREADDOC_UPLOAD you will find many of the requested fields already:
EABL-SERNR => BAPIEABLU-SERIALNO
EABL-ZWNUMMER =>REGISTER
EABLG-ABLESGR
EABL-V_ZWSTAND
EABL-N_ZWSTAND
EABL-ABLHINW
EABL-ZSKIPC
EABL-ADAT
EABL-ATIMTATS => ACTUALMRTIME
EABL-ADATTATS => ACTUALMRDATE
EABL-ATIM
EABL-ZMESSAGE
EABL-ABLESER(Meter reader number)
Field EABL-ZMESSAGE appears to be custom field (at least I cannot find it on ECC 6.0). If this field was added using include CI_EABL then you probably can get these values into the BAPI using the EXTENSIONIN parameter.
Check routine CHECK_UPLOADRECORDS in the BAPI which allows two extension structures:
- BAPI_TE_EABL
- BAPI_TE_EOSB
Not surprisingly BAPI_TE_EABL contains the include CI_EABL.
Regards
Uwe -
Problem with user exit EXIT_SAPLIEDI_001 for Inbound Idocs in replacing G/L
Hello all,
I am currently facing an issue where my IDOC where exit EXIT_SAPLIEDI_001 is not appearing to work properly.
Basically I am using the FM that processes the inbound idoc (IDOC_INPUT_INVOIC_FI) to post an accounting document. We needed a solution where we need to substitute one of the G/L Accounts.
The current process in our SAP system is that we are creating a billing document which automatically generates the output type (running: program rsnasted subroutine edi_processing) to create and process the inbound idoc.
So I discovered FM EXIT_SAPLIEDI_001 which exports company code and G/L Account back does this.
In this exit, Since I needed to get data from the IDOC, I used the logic ASSIGN: ('(SAPLIEDI)IDOC_DATA[]') TO <fs_edidd> to get the DATA Records for further processing.
During the development and testing phase in the Sandbox system this works.
However when we moved this to production we encountered a situation where the G/L account was not being substituted so were assuming EXIT_SAPLIEDI_001 is not working properly. However when I reprocess this in production either by running the idoc with errors RBDMANI2 or BD87 the IDOC is properly posted and the G/L Account is substituted as well as if I try to repeat the output type of the billing document. So there are instances when in the actual business scenario it does not work except when I reprocess it.
I was wondering if there are any ideas why this could have happened?
Oh ... I also noticed when we transported the objects of the exit. When I try to double click the subroutine I made inside the exit it said the object does not exist. I had to generate the function group of FM EXIT_SAPLIEDI_001 in SE80 in production for it to reflect. I was wondering if this could have caused the issue.
Well I hope to hear from you.
Regards
Edited by: Rob Burbank on Dec 6, 2011 1:03 PMHi,
Check in t.code CMOD whether project is active or not (Activate the Project)
BR,
Vijay -
I am testing creating Sale Order from inbound IDOC with WE19.
Partn. number = AAA001
Partn. type = KU
Partn.func = PY
Message Type = ORDERS
Process Code = ORDE
I get message 51 "Error: Application document not posted" in IDOC status:
VKORG, VTWEG, SPART cannot be determined for customer AAA001 , vendor
Message no. VG 204
Diagnosis
No sales organization, distribution channel or division were sent to the
IDOC. This data is necessary if a sales order is to be added
automatically. If this data is unavailable, you cannot create a sales
order document.
Procedure
If data on the sales organization, distribution channel and division
have not been entered in the IDOC, it must be determined using a user
exit defined in the program.I will receive IDOC from external non-SAP system.
How can i populate E1EDK14 segment with appropriate values:
E1EDK14 -QUALF = 006
E1EDK14 -ORGID = Division (VBAK-SPART)
E1EDK14 -QUALF = 007
E1EDK14 -ORGID = Distribution Chanel (VBAK-VTWEG)
E1EDK14 -QUALF = 008
E1EDK14 -ORGID = Sales Organisation (VBAK-VKORG)
If external system does not know this values?
Edited by: S S on Feb 28, 2009 12:46 PM -
Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed RoshanThank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan
Maybe you are looking for
-
I construct a JTree with objects which are extract from a data base. The extraction is filtered. I have to rebuild the JTree when I change the filter because the objects are different under the first stage after the root. Can somebody give me the met
-
Hi guys, I have the following problem with bookmarks. The bookmarks store navigation state of the web template. The problem is, if I create a couple bookmarks und after that I change something in the web template (e.g. add additional dropdown item)
-
"Pin" and "New Window" buttons in jDev
Hello all! In jDev 11.1.2.1.0 I can't find the "pin" and the "new window" buttons of the structure panel. I think that these two useful utilities could be found in the property window as well. Does anyone know if there are missing or I have to do sth
-
Factory reset my ipad but now its saying the activation server isnt available can anyone help
factory reset my new ipad but it is now saying that the activation server isnt available, has anyone got any ideas please?
-
Hi I have a laptop Dv7 2211. and the usb is not working the error message is the usbsential is not
Hp Pavillion DV7 2211Tx windows 7 32bit is saying usbsential is not working . Can anyone help?