Configuration on triggering an EDI IDOC

Hi all experts,
I have one issue here claiming that when intercompany billing is perform IDOC document should be generated to create posting in AP10 but now the IDOC is not generated and not posting to AP10.
Is there any settings that I need to do to trigger the EDI and generate the IDOC for this company code AP10? Should I maintain the AP10 under the partner profile we20?
How should I solve this issue
Details:
message type -- INVOIC
Please help and Thanks a lot~
Cheers

Hi,
Check whether the EDI message control (or output control) setting are configured properly.
Check the link - http://www.erpgenie.com/sapedi/messagecontrol.htm
You can also refer to SAP help for more details: http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/19878343b111d1896f0000e8322d00/frameset.htm
Hope this helps.
Regards,
Gajendra.

Similar Messages

Configuration to trigger the EDI IDOC when posting

Hi all,
Can I know what is the configuration needed in order to trigger the EDI message type INVOIC IDOC when posting to certain company code (eg: AP10)?
As I know for order acknowlegment need to do some configuration in Tcode v v13 in order to trigger the EDI...
Please help.
Thanks a lot.

Hi,
Please refer the below link:
SAP IDoc Configuration Overview:
http://www.topxml.com/biztalkutilities/walkthroughs/SAP%20IDoc%20Configuration.pdf
SAP Network Blog: IDOC: EAN mapping in EDI orders:
/people/michal.krawczyk2/blog/2006/12/22/idoc-ean-mapping-in-edi-orders
Hope this helps.
Please assign points as way to say thanks

EDI IDOC Configuration steps

Hi,
Can anyone provide me the step by step configuration of EDI IDOC ofr both incoming and outgoing mainly for PO.
Thanks
Regards,
Srivatsan

hi,
Refer SAP Note No. 455140
Refer SAP Note No. 546147
Refer SAP Note No. 607108
Refer SAP Note No. 779972
May be it will help you
Thanks & Regards,
Kiran

Port Configuration EDI/IDoc

Please anybody can explain me in detail Port Configuration for EDI/IDoc(T Code WE21).
please explain how can i create new port.
it's urgent please.
thanks
RP

rp
check the following links
http://help.sap.com/saphelp_47x200/helpdata/en/af/7e844367c24d4a950df3205052769d/frameset.htm
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

Problem in triggerring EDI idoc for Purchase order..

Hi experts,
I am trying to create an outbound EDI IDOC for a PO.
I have configured the partner profile in partner type LI with message type ORDERS in outbound parameters. I have created a new output type ZEDI for EDI, and entered in a message control, as application EF, message type ZEDI and process code ME10.
But when i go to the me23n and goto--> messages, but when i click F4 for output type i am not able to see the new output type ZEDI i have created.
And if i also enter NEU with medium EDI, and Partner function VN, and partner 3000(where i configured the parnter profiles), its giving an error as, "maintain outgoing EDI-connection data for partner 3000".
Kindly help me out. please experts reply me..
Nithin

Hi
In the transaction NACE
you need to maintain the necessary 'Z' output type, in your case.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Sales Process And EDI Idocs Integration

Hi Friends,,
Good Day To You All !!!!
Please enhance my knowledge with your valuable reply.
I am new to ABAP and would like to learn the following .
1. Sales process - Starting from the Purchase Order Till shipment is created (All TCodes and the definations of the terms used like procurement , scheduled line,handling unit and all those terms coming into picture till the Sales process comes to an end).
2 . Idocs - Transaction Codes,Definations Of Terms like message types , basic types etc, etc,
I need the above information to get a clear picture of the process taking below.
What if an interface exists between SAP and a Non-SAP system(say Siebel system ) .The customer being the Non-SAP system and the Vendor our SAP system . Then the flow of the sales process taking place , with the PO coming from the Non-SAP system through inbound idoc and immediate ATP date going from SAP through the outbound Idoc..the process continues with the creation of delivery then shipment.Each of these triggering their respective idocs .
And the idocs update the corresponding status in Siebel .
I hope you guys would have understood by now , as to why i need the information on Sales Process and Idocs.
Thanks.
With regards,
Learner .
Edited by: SAP Technical Consultant on Oct 16, 2008 9:08 AM

Hello,
         If you want to Set up an Inbound Process for Sales Order Changes, all you have to do is
1. Maintain the Partner Profiles for the Inbound Message Type & Process Code in WE20.
2. The Assignment for Function Module IDOC_INPUT_ORDCHG is already available in WE42 Transaction for the Process Code ORDC. So, you don't have to worry about setting up the Process Code.
3. Take a Sample IDoc of Type ORDCHG Message Type in WE19 and try posting it for the Given Sales Order. If you would like to know more about what it does, Post it using Debugging Mode.
            The above Process is for Sales Order Changes via Inbound IDoc. Below are the Steps for the Outbound Delivery IDoc Trigger.
1. The Process Code DELV already has the Selection Program IDOC_OUTPUT_DELVRY in Transaction WE41. So, you dont have to worry about Setting Up the Process Code.
2. Also, check your field list. Open the IDoc Type DELVRY05 in the Transaction WE60 which is for IDoc Documentation. Check if all the Fields mentioned in your the list that you want to send are available in the Standard IDoc Type. If not, create a Custom Segment in WE31 & Assign the Custom Segment at an appropriate place in the Extended IDoc Type in WE30.
     All the Standard Segments / Fields available in the DELVRY05 IDoc Type will be automatically be populated by the Standard Selection Program IDOC_OUTPUT_DELVRY. However, if you have an IDoc Extension and would like to populate the Custom Segment / Fields, then you'll have to use the Customer Exit EXIT_SAPLV56K_002 in which you can write Code for populating the Custom Segments / Fields.
3. The Most important Thing that we need to take care of is Message Control Configuration while handling the Outbound EDI Scenario.
4. You need to Set up the Output Type for the Delivery Application (V2) for which you need to maintain Condition Records so that the Output Type is proposed automatically when the Delivery is being Saved.
5. In general, the Message Control Configuration is done by the Functional Team. So, ask your Functional Consultant to set up the Message Control Configuration for the Delivery IDoc Trigger.
Hope it was clear enough.
Thanks and Regards,
Venkat Phani Prasad Konduri

What is Ale, Edi,IDoc tech for sap

Hi all,
What is Ale, Edi,IDoc tech for sap?
Thanks.

hi deniz,
ALE
ALE
Triggering OB via Change Pointers:
 When an application make a changes in any object an entry is made in CDHDR and CDPOS tables. When any change is made the SMD(Shared Master Data) Tool checks that ALE setting and create a change pointer in the BDCP table that will point to CDHDR table. A standard program RBDMIDOC is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process to distribute to the appropriate destinations. The program will read the table TBDME to determine the IDoc selection program it is MASTERIDOC_CREATE_SMD_MATMAS in the case of MATMAS.
Outbound Process:
When the stand-alone program or the Transaction(BD10) is run, it calls the Idoc
Selection program MASTERIDOC_CREATE_REQ_MATCOR in the case of MATMAS, which is hard coded in the program. The Idoc Selection program reads the master data and create a master Idoc and stores it in the memory. The function module then calls ALE layer by using another function module MASTER_IDOC_DISTRIBUTE which is invoked inside it. Then Idoc filtering, Segment filtering etc.. are done in the ALE layer.
 To dispatch the Idoc to the destination system, the system reads the partner profile to determine the destination system. Then the sending system calls the function module INBOUND_IDOC_PROCESS asynchronously on the remote system and passes the Idoc via memory buffer.
Asynchronous Communication:
The data that is IDocs and the function module are stored in ARFCDATA and ARFCSSTATE tables. The function module ARFC_DEST_SHIP will transports data to target System and the program ARFC_EXCUTE will execute the stored function Module. If communication problem occurs RSARFCSE program is automatically scheduled., if successful, entries in the tables ARFCSSTATE and ARFCDATA will be deleted.
Inbound Process:
The INBOUND_IDOC_PROCESS program is triggered as a result of RFC from the Sending System, the Idoc to be sent is passed as parameter for the function module
In the partner profile if Process immediately is selected then RBDAPP01 program is executed. It will read the process code(MATM) from the Partner profile, which in turn invoke the function module IDOC_INPUT_MATMAS for MATMAS
 Function module will call the corresponding SAP transaction using call transaction or uses direct programs to convert the Idoc to Application document .
In the table TBD51 there will be entries to find which option is used.
Transactions:
SALE - IMG ALE Configuration root
 WE20 - Manually maintain partner profiles
 BD64 - Maintain customer distribution model
 BD71 - Distribute customer distribution model
 SM59 - Create RFC Destinations
 BDM5 - Consistency check (Transaction scenarios)
 BD82 Generate Partner Profiles
 BD61 Activate Change Pointers - Globally
 BD50 Activate Change Pointer for Msg Type
 BD52 Activate change pointer per change.doc object
 BD59 Allocation object type -> IDOC type
 BD56 Maintain IDOC Segment Filters
 BD53 Reduction of Message Types
 BD21 Select Change Pointer
 BD87 Status Monitor for ALE Messages
 SALE Display ALE Customizing WEDI - ALE IDoc Administration
 WE60 - IDoc documentation
 SARA - IDoc archiving (Object type IDOC)
 WE47 - IDoc status maintenance
 WE07 - IDoc statistics
BALE - ALE Distribution Administration
 WE05 - IDoc overview
 BD87 - Inbound IDoc reprocessing
 BD88 - Outbound IDoc reprocessing
 BDM2 - IDoc Trace
 BDM7 - IDoc Audit Analysis
 BD21 - Create IDocs from change pointers
 SM58 - Schedule RFC Failures
EDI
EDI(Electronic Data Interchange )
RFC DESTINATION:
 A logical name used to identify the remote system on which a function needs to be executed.
Partner Profile:
 It defines the characteristics of data being exchanged with the business partner.
Partner Function:
 Role of the partner Eg:Ship-to-party,bill-to-party,etc in EDI and in ALE legacy system or remote SAP system.
Partner type:
 The type of your business partner .
 EDI KU/LI
 ALE -- LS.
Archiving:
 -Need to archive the important transmitted document
-Created in SARA
 -Assigned in WE20.
PartnerProfile Tips:
 RSECHK07- Consistency check for Partner Profile.
 If you want to modify partner profile; copy it and then modify. If you cant modify it , u have to delete it.
 To move partner profile to production system choose Partner -> Transport
Port defintion:
 It defines the medium through which data is exchanged between systems.
 tRFC - Used by ALE
 FILe - Used by EDI
 R/2 system system port For R/2 system
 Internet port - to connect with internet applications
 It also depends on the receiving side. If the receiving subsystem accepts tRFC, EDI also can use tRFC.
Remote Function modules required by Subsystem to send status and inbound idoc to SAP:
Startrfc - Program to execute RFC enabled Fun.mod. in SAP
EDI_DATA_INCOMING - To send data as inbound
EDI_STATUS_INCOMING - To send status to SAP
RSPARAM - To know the gateway service of the SAP system.
Message Control:
 Output controller
 A service program for determining the output type
 To generate and manage various outputs from an application and control their medium and timing of exchange.
 To retransmit the document without duplicating it
Procedure:
 A procedure defines a set of possible outputs for an application
 There may be more than one procedure but only one can be active
 Requirement field in procedure specifies the condition which the sales docu. should reach,for sending the sales order response.
Output type:
Defines the characteristics and attributes of the output.
Access Sequence :
Defines a sequence in which the business rules are checked using condition record of the condition table for proposing output type.
Sapfans Q & A
SREL_GET_NEXT_RELATIONS -
Function Module that will provide me the number of the document that was created by an IDoc
RLSUB020
Program which uses the above function module.
Upgradation problem
When the old version program is upgraded in to newer version(4.0b  4.6c) the SE38 editor wont allow u get thru the programs normally to get rid of this.
Solution:
EDIT > MODIFICATION OPERATIONS > SWITCH OFF ASSISTANT. Hit Enter on the subsequently shown Warnings window. You should now be able to maintain the code as before.
When transporting the dialog program sometimes the links may be missing in the testing and production area. To overcome just check u have properly save your all includes and other stuff in the same request if not, do so. Other options In ver 4.6c -> Within ABAP editor try utilities/Update navigation index
this fixes the links
ALE( Application Link Enabling )
Disk Mirroring:
Changes occurring in the database should reflected to another disk that maintains a mirror image of the main disks contents.
Replicas:
Maintaining redundant data across multiple systems.
ALE:
It provides distributed environment to integrate non-SAP systems
Provides guaranteed delivery of data regardless of network problem to application.
Logical system :
 The systems involved in distributed environment are assigned a logical name which uniquely identifies a system in a distributed environment.
Data Mapping:
 Conversion of a business document in IDoc format to an EDI format (and vice versa) which is performed in the subsystem.
Message Types:
 Represents a business function
 Technical structure is the IDoc type
 Or can say an instance of IDoc.
IDoc :
 They are containers used to exchange data between any two process.
 It represents an IDoc type and IDoc data
 IDoc type is structure and IDoc data is an instance of it.
Pls reward if helpful.

How to find the Program that triggered the outbound idoc

Hi,
I need to find the program that triggers a particular Outbound IDoc.
I have the IDoc number/segment/message type.
We need to Debug the Outbound IDoc but we do not know from where the IDoc got triggered.
Is there a way we can find which program triggered it?
Thanks!

Hi Suresh,
Go to tcode WE20, select ur partner profile type, which configured in output type for EDI documents.
On right side, double click on the Message type in outbound parameters.
go to message control Tab, double click on process code variable to see FM triggers for the IDOC.
same as for Inbound also.
Regards
Syed A

How to Send Purchase Order through EDI/IDOC.

Hi Experts,
We are using SAP ECC.5. And intending to send the Purchase Order to Supplier through EDI/IDOC and Receive the Inbound Acknowledgement.
Appreciate, if you could help me, the required Configuration details for outbound and inbound (PO & Acknowledgement).
Reg
Kumar

Hi Kiran
Many thanks for the response. It is true that by changing the message type to EDI can generate idoc. What is not clear is any other config we need to do interms of Message generation, Resubmitting failed IDOC etc..
Out requirement is that we would generate the IDOC for New and changed docs and send to external EDI converter.
Inbound, receive the IDoc and post the acknowledgement.
Appreciate, if you could forward any document link which can explain the details.
Reg
Kumar

EDI/IDOC setting

Hi,
Can anybody suggest regarding any EDI/IDOC setting for SD counsultant apart from developer's work?
Regards
Susrikant

Apart from output there is nothing in SPRO, but there is lot to be done in WEDI.
To understand the basic configuration adn teh setup reqmt for IDOCs, EDI, you can go through the following links.
Then you will understand the configurations needed.
http://www.riyaz.net/blog/index.php/2008/01/19/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
http://www.scribd.com/doc/24447/SAP-R3-IDoc-Cookbook-for-EDI-and-Interfaces-by-Axel-Angeli
This one is really good, try to complete the book
http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
Hope this helps.
You can reward if this helps you

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.

How to file data from sap server to third party-tibco using EDI-Idoc?

Hi all,
I need to send data from sap server to third party system in th form of file.
Please guide me how to send data file from sap server to third party-tibco using edi-idoc?
Also guide the configuration ti be done for EDI.
Thank you.

1)create file port
2)TCP-IP RFC destination with a program RFCEXEC to be executed on application server
3)Dummy distribution model
4)Partner pofile of type other han LS

QM Block not triggered via EDI orders

Hello All,
Please help me with this problem "QM block not triggered via EDI Orders".
Sales Orders will be created using IDOC. When the sales orders was displayed using VA02, goto >> items >> schedule lines, there's no QM status violated being displayed in the delivery block column.
Kindly help me what logic will I applied regarding this matter.
FM used was IDOC_INPUT_ORDERS.
I need your comments/suggestions ASAP.
Thanks in advance.
Carina

hai,
Just check this it may help tou.
Program Name : YX30_UPLOAD_QUALITY_INFO
Quality Info Record for I30 System *
Original Transport Number : I30K903055 *
SYS id: SYS_30_1502_03_41_Upload Quality Info Records *
TDS id: TD_30_1502_03_41_Upload Quality Info Records *
UT ID: UT_30_1502_03_41_Upload Quality Info Records *
======================================================================
Change History *
Date | Change No | Name | Description *
yyyy/mm/dd | AAAYYYYMMDD | xxxxxxxxxxxx | *
REPORT YX30_UPLOAD_QUALITY_INFO MESSAGE-ID yx30_conversions
no standard page heading line-size 255.
include yx30_upload_quality_info_top. "Include for Variable Declaration & Selection Screen
include yx30_upload_quality_info_data. "Include for File read & Authority Check
*& At Selection Screen Output *
AT SELECTION-SCREEN OUTPUT. "PBO
PERFORM fill_parameters.
*& Start Of Selection Event *
start-of-selection.
Perform Authority_check. "Subroutine for authority check
Perform prepare_file. "Subroutine for preparing file
perform file_read. "Subroutine for File read
perform update_qi01. "Subroutine for Uploading data
perform write_error_log1. "Subroutine for writing error log
*& Form write_error_log
text
--> p1 text
<-- p2 text
*& Include YX30_UPLOAD_QUALITY_INFO_TOP
Type Declaration
Types: Begin of type_qtyinf,
matnr type matnr, "Material No
lieferant type char10, "Vendor
werk type werks_d, "Plant
frei_dat type char10, "Frei_Dat
stsma type char8, "Stsma
anwso_01 type char1, "ANWSO(01)
anwso_02 type char1, "ANWSO(02)
anwso_03 type char1, "ANWSO(03)
end of type_qtyinf.
Internal Table Declaration
Data: itab_qtyinf type standard table of type_qtyinf. "Internal table for QTYINF.
Work Area Declaration
Data: wa_qtyinf type type_qtyinf. "Work Area for QTYINF.
Variable Declaration
Data: v_file_qtyinf type string, "Source File Name
v1 type string,
v2 type string,
v3 type string,
v_file_return type string,
v_lin TYPE n.
*Selection Screen Declaration
selection-screen *
SELECTION-SCREEN BEGIN OF BLOCK blk1
WITH FRAME TITLE text-s01.
PARAMETER:
p_sysid(3) TYPE c OBLIGATORY , "Source System
p_bukrs(4) TYPE c OBLIGATORY , "Source CompCode
p_samshr type char30 lower case obligatory default '/sap_upload/' , "Samba Share Drive
p_object TYPE CHAR10 OBLIGATORY default 'MAT' . "Migration Data Object
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN SKIP 3.
PARAMETER:
cb_pfill TYPE c AS CHECKBOX DEFAULT 'X' . "Prefill values?
SELECTION-SCREEN COMMENT /1(79) text-s1a.
SELECTION-SCREEN BEGIN OF BLOCK blk3
WITH FRAME TITLE text-s03.
PARAMETER:
pa_filn1(500) TYPE c LOWER CASE
VISIBLE LENGTH 50 , "Filename AppServer
pa_dlimt TYPE c DEFAULT ';' . "Field Delimter
SELECTION-SCREEN END OF BLOCK blk3.
include bdcrecx1. "Include for the subroutine
*& Include YX30_UPLOAD_QUALITY_INFO_DATA
*& Form file_read
Subroutine for reading the source file into internal table
--> p1 text
<-- p2 text
FORM file_read .
DATA:
single_line TYPE string .
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_qtyinf FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
DO.
READ DATASET v_file_qtyinf INTO single_line. "Reading the content of file into line
IF sy-subrc = 0.
IF sy-index > 1. "skip header-line
SPLIT "Split the content of line into work area
single_line
AT ';'
INTO
wa_qtyinf-matnr "Material No
wa_qtyinf-lieferant "Vendor
wa_qtyinf-werk "Plant
wa_qtyinf-frei_dat "Frei Date
wa_qtyinf-stsma "STSMA
wa_qtyinf-anwso_01 "ANWSO_01
wa_qtyinf-anwso_02 "ANWSO_02
wa_qtyinf-anwso_03. "ANWSO_03
APPEND wa_qtyinf TO itab_qtyinf. "Appending Work Area to internal table
ENDIF.
ELSE.
EXIT.
ENDIF.
ENDDO.
CLOSE DATASET v_file_qtyinf. "Closing the files
ELSE.
MESSAGE e015 .
ENDIF.
DESCRIBE TABLE itab_qtyinf LINES v_lin.
IF v_lin LT 0.
MESSAGE e016 .
ENDIF.
ENDFORM. " file_read
*& Form fill_parameters
Subroutine for getting the file name
FORM fill_parameters .
IF cb_pfill = 'X'.
Preparing QTYINF File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO pa_filn1.
ENDIF.
ENDFORM. " fill_parameters
*& Form Authority_check
Authority Check
--> p1 text
<-- p2 text
FORM authority_check .
Authority Check For the Migration
AUTHORITY-CHECK OBJECT 'YX30_MIGR'
ID 'SYSTEM' FIELD p_sysid
ID 'BUKRS' FIELD p_bukrs
ID 'YX30_DMOBJ' FIELD p_object
ID 'ACTVT' FIELD '16'.
IF sy-subrc <> 0.
MESSAGE e010 WITH p_sysid p_bukrs p_object.
ENDIF.
ENDFORM. " Authority_check
*& Form prepare_file
text
--> p1 text
<-- p2 text
FORM prepare_file .
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_QTYINF_' p_bukrs '.CSV' INTO v2.
CONCATENATE p_samshr v3 '/' p_object '/' v2 INTO v_file_qtyinf.
CLEAR v3.
CLEAR v2.
Prepare Return File
CONCATENATE p_sysid '_forward' INTO v3.
CONCATENATE p_sysid '_RETRUN_LOG_' p_bukrs '.CSV' INTO v2.
CONCATENATE '/sap_upload/' v3 '/' 'MAT' '/' v2 INTO v_file_return.
ENDFORM. " prepare_file
*& Form update_qi01
text
FORM update_qi01.
PERFORM open_group. "Opening a session
CLEAR wa_qtyinf.
LOOP AT itab_qtyinf INTO wa_qtyinf.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0100'. "Subroutine for mapping data
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-MATNR'.
PERFORM bdc_field USING 'BDC_OKCODE'
'/00'.
PERFORM bdc_field USING 'QINF-MATNR'
wa_qtyinf-matnr. "Mapping the material
PERFORM bdc_field USING 'QINF-LIEFERANT'
wa_qtyinf-lieferant. "Mapping the vendor
PERFORM bdc_field USING 'QINF-WERK'
wa_qtyinf-werk. "Mapping the plant
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=STAN'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-STSMA'.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma. "Mapping the status
PERFORM bdc_dynpro USING 'SAPLBSVA' '0201'.
PERFORM bdc_field USING 'BDC_CURSOR'
'J_STMAINT-ANWSO(01)'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=OKAY'.
IF wa_qtyinf-anwso_01 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01. "Mapping the anwso(01)
ELSEIF wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02. "Mapping the anwso(02)
ELSEIF wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03. "Mapping the anwso(03)
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ELSEIF wa_qtyinf-anwso_01 = 'X' AND wa_qtyinf-anwso_02 = 'X' AND wa_qtyinf-anwso_03 = 'X'.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(01)'
wa_qtyinf-anwso_01.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(02)'
wa_qtyinf-anwso_02.
PERFORM bdc_field USING 'J_STMAINT-ANWSO(03)'
wa_qtyinf-anwso_03.
ENDIF.
PERFORM bdc_dynpro USING 'SAPMQBAA' '0101'.
PERFORM bdc_field USING 'BDC_CURSOR'
'QINF-FREI_DAT'.
PERFORM bdc_field USING 'BDC_OKCODE'
'=QMBU'.
PERFORM bdc_field USING 'QINF-FREI_DAT'
wa_qtyinf-frei_dat.
PERFORM bdc_field USING 'QINF-STSMA'
wa_qtyinf-stsma.
PERFORM bdc_transaction USING 'QI01'.
ENDLOOP.
PERFORM close_group. "Closing the session
ENDFORM. "update_qi01
*& Form write_error_log
text
--> p1 text
<-- p2 text
FORM write_error_log1 .
DATA:
single_line TYPE string,
v_msg TYPE string,
v_msg1 TYPE string.
*-- read file, split lines into fields and put data into table
OPEN DATASET v_file_return FOR INPUT IN TEXT MODE ENCODING NON-UNICODE. "Opening the files
IF sy-subrc EQ 0.
CONCATENATE text-020 v_lin INTO v_msg SEPARATED BY space.
CONCATENATE text-021 v_lin INTO v_msg1 SEPARATED BY space.
TRANSFER: v_msg TO v_file_return.
TRANSFER: v_msg1 TO v_file_return.
WRITE:/ v_msg.
WRITE:/ v_msg1.
ENDIF.
ENDFORM. " write_error_log
with regards.
sowjanya.b.

GTS - EDI IDOC Set up

Hi,
We need to set up the EDI IDOC for communicating with Agent and to receive the confirmations from Agent (both outbound and Inbound) to GTS. This is to be done for Export and Import declarations.
Please share the configuration information to set up in the system for the above scenario.
Regards
Nag

Have you defined both Quantity and Value updating in your license type? If so, what about only depreciating by quantity (instead of value). Not sure if I am reading you correctly, but from your example it seems that you are only concerned with quantity (and not value) depreciation, as you want to first exhaust the quantity available from License A (5), and then take the remaining from License B (5)..
Please let me know if this is helpful...

EDI IDOC OUTBOUND send Purchase Orders from sap to vendors

Hi Experts,
I am new to EDI IDOCS, but i got object on this. So my requirement is purchase orders are send to vendors from sap (OUTBOUND) through EDI-850 format. and also i have to add some more fields to standard idoc type ORDERS05, one more condition is if vendor type is not EDI, then the POs should send through fax, email, how can we solve this condition.
So plaese send some sample code on this object.
Thanks in advance,
S Reddy

Hi ,
You can send the purchase order to the vendors using different outytpes configurations in NACE transaction .
If you define a particular output type where you need to give medium 6 and define partner functions within this you can also set condition which partner needs to recieve EDI output and which one FAX or email all this will be done by Functional expert.
For adding extra segments to your basic type ORDERS05 you need to extend the idoc you can do it via WE30 and WE31 .Link you message type to basic type and extension . Please follow below tcodes for further help . Create all the requested steps in the tcodes mentioned below.
we20:patner profile
we21:port
we30:idoc creation
we30:segment creation
we81:message type
we82:link message with idoc type.
we02:to status of idocs.
Now you need to write code for filling those extra segments you have added to you extension type. For that you need to check where your new segment is placed in Idoc structure . There will be a exit avaliable to attach your code to fill those segments .
Please go through previous SDN links to see more info.
One the settings are done in the NACE , issue output from PO transction and once your output is processed check your Idoc in WE02 to see if the segments are coming with the desired data.
Regards
Vikas

Configuration on triggering an EDI IDOC

Similar Messages

Maybe you are looking for