Re:PO creation idoc

HI,
here we are using Process code : ME10 for PO creation Idoc. my problem is "idoc is not generated automatically", if we enter values manually idoc will gwt genarated.
message control and partner profile every thing is correct,in the output condition records we have metioned immediate processing (4).
regards

thanks for valubul inputs

Similar Messages

Planned order creation IDOC

Hi Experts,
i've a requirement where i need to develop a custom IDOC for Planned order creation. is there any standard IDOC for Planned order creation and if it is there then provide me the complete details like IDOC name, message type name, posting and selection program names etc.
if i need to create a custom idoc then wht is the procedure for it.
Regards
Faisal

Hi Abdul,
You can use the below details for achieving the below requirement:-
Message Type :- LOIPLO
Basic Type :- LOIPLO01
You need not create any custom IDOC type as we are having a standard IDOC type available within SAP, but you need to write a custom function module to read the data from the IDOC segments and then call the below BAPI to post the Planned Order.
Check the input parameters of BAPI and gothrough the documentation of the Basic Type in WE60 transactions, whether all the necessary input parameters of the BAPI are covered in the standard IDOC type, if not then we need to customize the standard basic type to meet the requirements.
Bapi which needs to be used is BAPI_PLANNEDORDER_CREATE.
I think all these inputs will solve your purpose.
Thanks,
Mahesh.

Source system creation IDoc error

Dear Experts,
While creating the source system I am getting this error "IDoc type ZSDD029 could not be found", if I ignore this error the system creates source system in BI folder instead of making it in SAP folder. I have created IDoc with this name and next time when I create new source system the IDoc type move to ZSDD030, and keep on adding it and gave me this error. Any Idea
Regards,
ray

Hello,
Can you try the following:
1) Tcode WE30: The type ZSDD029 must exist in BW system.
If it does not exist, create it as a copy of type RSSEND.
2) Afterwards, enter the following in the view maintenance of view
EDIMSG (tcode SM30):
Message type RSSEND, IdocType as specified above, Release
corresponding to the release you are currently using.
3) Please make sure your entries for RSBASIDOC are identical in BW.
Regards,
Shashank

ProgramID creation/IDOC monitor

Hi
I have done scenario BAPI-XI-IDOC using XSLT mapping.
I'm calling BAPI on same server(R/3) and posting IDOC on same(R/3) .
1. but unable to find any mesages in SXMB_MONI and MessageMonitor in RWB?
2. I dint find any IDOC adapter running in component monitor? I'm able to see other adapters expect IDOC and HTTP..why?
3. I thought ProgramID may be wrong with here, thats the reason i couldn't see any request message in sxmb_moni.?
4. For this i have created two Businesssystems as thirdparty for sending and receiving, Is it right?
5. I dint create sender aggrement! is it right?
6. for this i'm trying to configure in SXMB_ADM as RUNTIME for LOGGING_SYNC to 1, but i couln't see Value 1.
Hope i'm clear about my queries, please give me reply when you get time.. note down right now i'm working with XI3.0SP9 evalution version.
Thank you ,
regards..rambarki

hi,
>>>2. I dint find any IDOC adapter running in component monitor? I'm able to see other adapters expect IDOC and HTTP..why?
not all adapter are visible in the adapter monitor
(only those which are on java stack)
>>>>3. I thought ProgramID may be wrong with here, thats the reason i couldn't see any request message in sxmb_moni.?
yes test the rfc dest in SM59 - does it work?
do you have any messages in SM58 on your R3 system?
>>>>4. For this i have created two Businesssystems as thirdparty for sending and receiving, Is it right?
use just one (the one from your R3)
>>>>5. I dint create sender aggrement! is it right?
no, you need sender agreement for RFC
(use the configuration wizzard to configure ID)
Regards,
michal

Check tax classification Customer creation (IDOC)

Hi all,
I am a beginner in SAP Abap and i need some help to resolve my IDOC problem.
I want to generate Customer migration. my segments for the IDOC are filled. I use the IDOC_INBOUND_WRITE_TO_DB to create my IDOCs. Also for some customers, an error occur with status 51 saying : Check tax classification; maintenance is incomplete.
Or in the E1KNVIM segment, the tax code is filled as follow :
CLEAR ds_e1knvim.
ds_e1knvim-msgfn = '009'.
ds_e1knvim-tatyp = ds_tax-tatyp.
ds_e1knvim-taxkd = ds_tax-taxkd.
and in the we19 transaction, i have tried to launch it foreground
with the tax code filled correctelly.
but the batch-input don't fill the tax code case.
But for some other customers, the tax code case is filled correctelly?
Did i messid something ?
Thanks for your answers.

Hi Julius,
Thnx for the reply.
No I am not maintaining any tax related settings & all the fields in R/3 in XD01 are optional. Can you please elaborate further as to wht Tax settings are you speaking about???
Many Thanx.
SP

SalesOrder creation IDOC

Hi Gurus,
Can you please provide IDOC type to create sales order . I have checked with orderise01 to 05 but it couldn't match the fields,Can any body provide correct Idoc type?
Thank you,
Usha.G

Hi Usha,
Check out ORDERS0<n>, where <n> between 1 and 5 (don't think there's a higher version than 5, but didn't check). This works fine for creating sales orders.
Cheers, harald

Idoc-XI-file test scenario

i m new to XI,
i wanna make a test scenario for idoc-XI-file...
i donno what an idoc is.......
tell me how to create an idoc from the very basics....like message type, segment, partner profile, port creation, etc,..... and how to fire an idoc from the R3 system to my XI system,
and ofcourse... ican do the rest of mapping and all, with the file message type

Hi Sudeep,
1. steps for creating customized Idocs..
we31- creation of Segments
we30- creation idoc types
we81- creation of Message types
we82- assigning message type to Idoc type...
2. R/3 Configuration settings
SM59 - creation of RFC destination...
we20 - creation of Ports
We21 - Creation of Partner profiles..
3. XI Configuration settings
SM59 - Maintain RFC destination,
IDX1 - Maintaining port for XI
IDx2 - Loading the Idocstructure into metadata repository
These are the settings to be done before starting ur scenario..
I think this will help you... points...
regds,
vasanth.

Fill IDOC segment, E1IDBW1. For PEXR2002 Basic Type

Hello Team.
We send the IDOC for the Basic Type PEXR2002, Message Type PAYEXT.
This IDOC doesn't fill the Segment E1IDBW1 (IDoc header - special instructions (INP) )
I'm review some notes(1164524) and said to fill this segment it's neccesarie config the IHC.
But doesn't have this functionality.
It's possible fill the segment E1IDBW1 in a user exit or any other enhacement at creation idoc moment?
My idea is used the FM
CALL FUNCTION 'GET_SEGMENT_POS_FOR_INSERT'
    EXPORTING
      I_BASIS_TYPE            = ch_edidc-idoctp
      I_EXT_TYPE              = ch_edidc-cimtyp
      I_SEGMENT_TYPE          = 'E1IDBW1'
    IMPORTING
      E_INDEX                 = li_tabix
    TABLES
      IT_EDIDD                = t_edidd
    EXCEPTIONS
      BASIS_TYPE_NOT_FOUND    = 1
      EXTENSION_NOT_FOUND     = 2
      EXTENSION_ERROR         = 3
      INVALID_IDOC_DEFINITION = 4
      IDOC_ERROR              = 5
      INVALID_SEGMENT_TYPE    = 6
      INVALID_START_INDEX     = 7
      NO_MORE_POSITION        = 8
      TOO_MANY_SEGMENTS       = 9
      OTHERS                  = 10.
To Fill 2 constants in this segment.
Do you have any other idea?
Thanks
Edited by: David Lezama Gonzalez on Sep 1, 2011 2:51 PM

Hi,
Basically the segment E1IDBW1 will always be filled via user exit.
If you work with the IHC (In-House-Cash) application you have to fill
the E1IDBW1 segment as described in note 626577.
If you don't work in an IHC environment the following conditions must
be fulfilled:
1. The payment program has to fill certain fields (e. g. REGUH-DTAWS,
REGUH-DTWS1 - REGUH-DTWS4).
2. If this is fulfilled the payment data (REGUH, REGUP tables) will
be filled. The instruction keys will be moved to IDOC segment
E1IDKU3.
3. In user exit EXIT_SAPLIEDP_002 you can take over the instruction
keys from segment E1IDKU3 into E1IDBW1.
You may also read note 496663, this note explains about user exit
EXIT_SAPLIEDP_002 to populate this field in the idoc.
Also, you can check the note:
580321 - RFFOEDI1: BTE process 00002441 (Change IDoc)
REgards,
Cristiano

IDoc Mapping Question

Hello all,
i have the mapping of an iDoc relevant to Inbound deliveries (Inbound Delivery for Purchase order).
in the mapping i see /E1EDK08/E1EDP07/E1EDP09/VRKME for 'unit of measure' or /E1EDK08/E1EDP07/BSTNK for 'PO Number this shipment links to'.
What I dont understand is how 2 segments can be relevant to one field i.e. VRKME.
In other mappings i.e. /E1EDP01/NETWR for P.O line item value in P.O creation iDoc is very clear.
I would be greatful if someone could explain the other cases
Thanks

Hi Ioannis,
the mapping represents the hierarchical structure of the IDOC: E1EDK08 header segment may have one or more E1EDP07 item segments with one or more E1EDP09 subsegments.
Where di you find those mappings? (never saw it in that way)
Regards,
Clemens

Requirements for IDOC

Hi friends,
Could you please tell me the details required for doign a IDOC scenario.
I want the details seperately when IDOC is a sender and also when IDOC is a receiver.
Note: High reward points for the reply

HI
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. 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.
Idoc creation
IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages) and the other is OUTBOUND PROCESS( IDOC is send to other system . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP IDOC type
MESTYP Message Type
RCVPRN Recieving Partner (Destination)
RCVPRT Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
INT_EDIDD-SEGNAM = 'ZSEGMENT'
W_SEGDATA-field1 = value "taken from some table
W_SEGDATA-field2 = value "taken from some table
INT_EDIDD-SEGDATA = W_SEGDATA
APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.
You can get the all description from below tcodes
WE60-> Documentation for IDoc types
WE09-> Search for IDocs by Content
BD87-> Status Monitor for ALE Messages
WE63 -- information about Standard IDOC in R/3
WE64 - Details about process codes
WE82, WE30, WE31 -- IDOC Types.
SAP R/3
R/3 to XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
XI to R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1) ( Create port to get IDOC Meta data from sender system)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
Details ABT IDOC??????
1)Use WE60 transaction.
2)you need list of basic type idocs then use t.code WE60.
To display IDOC list in particular time intervel use we02 or we05.
where u can find the outbound and inbound processing idoc's.
use t.code 'wedi' to get more information on idoc's.
3)You can use the WE60 for Idoc Documentation
& we can use WE30 for Idocs list
Refer the below links for furtehr assistance
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
cheers

Idoc distribution with status of error records.

Hi Gurus,
my business requirement is i want to creat the Outbound Interface to distribute the data from sapserver to ESB server using the one userdefined function module, in this custom function module i written the logic to validate the input data if validation is file those error records are updated to one return table parameter and using the FM Master_Idoc_distribute for create and distribute the sucessfull records. till its working fine (with status 30-ready to dispach, 01- idoc creatd is in we05 and i have done the all configaration of message type creation, idoc type creation, port, partnerfrofil) ,
but my requirement is , for example if in 10 records even one record is also error records then no need to distribute the idoc data to sending system, just i want to send the idoc number with status error with error message.
plese suggest me the appropriate procedure.
Thanks & Regards,
Sai Ram.

Hi,
in ur code ur filling the idoc data rcord, control record ryt ..before u append data to idoc data , u r also validating and u might be doing in loop for appening the idoc data.
if there is any error in idoc then it won't distribute the data, it will be in error status only..u can only see the data in WE02. Then u can also change the data in WE02 and redistirbute it via BD87.
if u have any conerns let me know
Regards,
Nagaraj

Item partner flag set in Orders06 Idoc

Hi,
I am trying to set the item partners flag in a sales order creation Idoc Order06. Unfortuantely I am not able to find a placeholder or a segment field to map this flag in the Orders06 Idoc. So I am not able to overwrite the ship to addresses coming inthrough the interfaces. Please advise.
Teresa

Thanks Ravi for response. i had super busy week could't get back.i think i could't not provide enough details about the issue.
we have maintained 6 different languages in material master in purchse order text tab-additional data Tab.
when i set the deletion flag in MDM .MATMASS idoc generates successfully and i can see field carrying deletion flag indicator and it does set deletion flag on ECC side but after that if i check the additional data tab where we have maintained the material description for 6 different languages i see only three left other three are wiped off.it also shows in change log that changes has been made in those value but not sure about the root cause.i want to set deletion flag but no change in description.
Thanks again for your interest.

Idocs for purchase order in SAP to SAP

Hi
I have to send purchase order from a SAP system to a SAP system, creation and modification both.
I found these Idocs:
ORDER in sender SAP
PORDCR for creation in destination SAP
PORDCH for update in destinaton SAP
My problem is that all of three idoc have different segments, so i have to map field by field: is there a different solutions, always using idocs and not BAPI directly?
Thanks lot.
Matteo Vernile.

Hi Matteo,
To send purchase orders you can use next Idocs:
1. Creation -->Idoc type: PORDCR102 Message: PORDCR1 This Idoc is based on BAPI_PO_CREATE1
2 Modification --> Idoc type PORDCH02 Message: PORDCH This Idoc is based on BAPI_PO_CHANGE
Using standard boldSAP message determinationbold you can create these Idocs without create any ABAP program.
If you are not creating the Idoc using the standard Message Determination, you should obtain the data using the bapi BAPI_PO_GETDETAIL.
Reward points if helps.
Regards,
Roger

PO Change O/P error- Maintain outgoing EDI-connection data for partner for

Hi Experts ,
We are connecting our SAP ECC 6 ( Ehp 4) sytem to 3rd party system via SAP PI. We already done all the settings..line Output detemination procedure, Partner Profile ( WE20) , Port creation , Condition Records..etc.
We have PO Creation ( ZCRE) and PO Change ( ZPOC) Outbound messages to go from our system. Both have sepate message Types, since PO Creation IDOc should go immidiatly ( Dispatch time 4-Send immediately (when saving the application)
and PO Change IDoC should send as per wish manully in ME9F ( Dispatch time -3 Send with application own transaction).
Once PO Created , Output Message successfully triggering and IDoC is creating ( Green Color) ..so it is working fine .
Fo PO Change Message we had selcted Program -FM06AEND & FORM routine -CHANGE_FLAG.
We also set "Multiple issuing " checkbox in the Output Type and no requierment is assigned.
In WE 20, for Logical system ( LS) Partner XYZ, we set Process code ME11 and checked "Change Message"
1. But when I change PO Qty , output is not automaticaly triggering .After changing PO, if we see determination Analysis, in Procedure RMBEF1, this output ZPOC shows 2 times. First, it shows green color,...Output Found , and second times, it displays, "partner XYZ is not an EDI partner"
2. If we try to manually enter the Output ZPOC in PO Header, then system gives the Error - Maintain outgoing EDI-connection data for partner XYZ.
Can anyone pls suggest what should be the reason for above?
Thanks
NAP

Issue Resolved .
The reason for this system behaviour is in fine-tuned control: We was
using ZMIN only for new message output and ZCHG only for change messagesNevertheless, you can maintain two entries in WE20 for ORDCHG:
EF ZCHG ME11 w/o Change message flag
EF ZCHG ME11 with Change message flag
Thanks

PO transfer ERROR with PORDCR1.PORDCR102 to SNC

Hi~
PO is transfered from ECC to SNC.
ECC Idoc "PORDCR1.PORDCR102 " -> SNC xml "RelenishmentOrderNotification"
In SNC, there are application error because of delivery_date field.
<Analysis>
When we create PO in T/C ME21N, we enter delivery date in PO item line with own date type.
But that field(EEIND) is Charater type, not Date type.
In idoc PORDCR1.PORDCR102 segment 11(E1BPMEPOSCHEDULE), DELIVERY_DATE field is also same as PO input data.
At the end, in SNC, Delivery_date field value is wrong value.
So Application error occured.
ex)
Own date type : DD.MM.YYYY
PO Item Delivery_date field(EEIND) : 28.02.2011
ECC Idoc DELIVERY_DATE field : 28.02.2011
SNC xml Delivery_date value : -<ScheduleLine> <StartDateTime>28.0-2.-20T00:00:00</StartDateTime></ScheduleLine>
<ECC Idoc setting>
We use processing routine program 'BUS2012_ICH_R3', FORM routine 'SEND_PORDCR1'.
Actually, PO creation Idoc ORDERS.ORDERS05 have no problem.
But there are no tax code and ESR indicator, so we changed Idoc message type.
Do you know the solution?
Bestregrads,
SKY
Edited by: Soon-Kyoung Yu on Feb 11, 2011 7:40 AM

Hi SKY,
You need to implement the BAdI for BAPI_PO_CREATE1 and BAPI_PO_CHANGE - BUS2012 with BAdI Definition ME_BAPI_PO_CUST and create Implementation Class CL_EXM_IM_ME_BAPI_PO_CUST in ECC to resolve this issue.
Path:SAP Customizing u2013> Implementation Guide --> Materials Management --> Purchasing --> Business Add-Ins for Purchasing ---> BAdIs for BAPI_PO_CREATE1 and BAPI_PO_CHANGE u2013 BUS2012.
Regards,
Nikhil

Re:PO creation idoc

Similar Messages

Maybe you are looking for