Enhancements to the INTERNAL_ORDER01 Idoc

Hi all,
I am implementing an ALE scenario and I need to modify the content of one of the fields of the Idoc. I have implemented the distribution model (using the BAPI_INTERNALORDER_SAVEREPLICA) and works fine, but I haven't found any user exit to implement code for change the value I need.
Any idea?
Kind Regards,
Alfredo Lagunar.

Hi,
you can get the exit in the fuction module IDOC_INPUT_ORDERS.
<REMOVED BY MODERATOR>
Many Thanks,
Sharath
Edited by: Alvaro Tejada Galindo on Jun 9, 2008 6:32 PM

Similar Messages

Enhanced Interface Determination for IDOCs

Hi All,
I've a query on the usage of Enhanced Interface Determination for IDocs.
I've to create IDocs based on the condition in the Message Mapping i.e. say if recordtype in the source is A then IDoc1 should be created and if recordtype is B then IDoc2 should be created.
Is it possible to use Enhanced Interface Determination to achieve this??.. Because I was told by someone that Enhanced Interface Determination can't be used for IDoc based scenarios though am using External Definitions for the mapping purpose. Please clarify.
Thanks in advance
Regards,
Joe.

Hi Sridhar/ Bhavesh,
Thanks for your prompt reply. I think I wasn't clear in my previous post.
The scenario is the input file has three different record types (3 different structures) and the IDocs should be created based on the record type. I don't think I can use the condition based scenario as the record types are totally different. Please suggest.
Thanks,
Joe.

Can We Add Some More Fileds To the Imported IDOC ??

Hi All,
Can We Add Some More Fileds To the Imported IDOC ??
If I Imported IDOC to IR. But I Want to Add Some More Fields To IDOC.
Then Can I Go For this Process ??? Is This is Correct ???
Please Correct Me If Iam Going Wrong
1) Open the Imported IDOC in IR
2) Export it as XSD File in to your Local Machine
3) Add Necessary Fields & Save it
4) Come to IR And Import it into external definition
Is this is the Correct way of Doing ???
If Not What is the Problem in Doing This ??
Regards
Vamsi

Hello Vamsi,
That is NOT the correct way to play around with IDOCs.
the correct way is to create an enhancement to an exiting IDOC (this is done on the SAP R/3 side) after you craeted an enhancment you reimport the IDOC in XI from the R/3 and then you have a new structure with the new fields you need.
worst case scenario you can define a new IDOC type just with the fields you need.
you can check out the SAP library at http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
on how to do that.
Have a good one,
Uri Lifshitz.

Validation the Inbound Idoc Cremas05

Hi ,
I have a requirement for inbound IDoc, my scenario is like this , we have to process the ADRMAS03 idoc first. This idoc will contain vendor number in OBJ_ID field .After that we have to process CREMAS05 idoc, at the same time we have to validate the vendor 's existence (which is in OBJ_ID field in ADRMAS03 idoc) . If vendor does not exists we don't want to process the CREMAS05 .
How to check whether the vendor is already exits when we process the CREMAS05 ?
In which table, the vendor number will store when processing the ADRMAS03 ?

Hello ,
It is an SAP Standard Interface created through BDBG. I would suggest you to create a similar interface using BDBG.
1. First create an empty BAPI( Copy of BAPI_GOODSMVT_CREATE) say ZBAPI_GOODSMVT_CREATE. Note the remove the logic of your Z BAPI.
2. Got to SWO1, create a deleagtion of BUS2017 called ZBUS2017 and a new Z API Method ZCREATEFROMDATA forr Z BAPI
Release and Activate.
3. Now go to BDBG and create an BAPI -ALE Interface.
You can write the custom logic and validation in your Z BAPI - ZBAPI_GOODSMVT_CREATE and finally call the standard BAPI BAPI_GOODSMVT_CREATE in it to post goods movement.
Advantage : 1. one less enhancement for SPAU, next upgrade.
2. Interface is generated automatically , only you need to take care of your custom code in Z BAPI.

How to change the default IDOC basic type from CREMAS05 to CREMAS04.

Hi All,
How to change the default IDOC basic type from CREMAS05 to CREMAS04 when sending Vendor Master Data.
When I generate partner profile, the system will add the latest version of IDOC type which is CREMAS05 to the Outbound message. In my project, I'm asked to use CREMAS04.
I want to use BD14 to send master data directly, but the program will generate IDOC using CREMAS05. Is there a way that I can change it to CREMAS04? And also for using Change Pointers, I want to use the report RBDMIDOC, but i have the same problem.
Thanks
Sai Krishna

execute WE20 and edit the outbound parameters
here is a pretty good example: http://documentation.softwareag.com/webmethods/sapr3_gateway/sap231/pages/sapdist.htm
Edited by: Jürgen L. on Sep 7, 2011 9:49 PM

How to update the Sent Idoc Status based on the Response From Webservice

Hi All,
I have to develop Idoc--SOAP Sync Process Scenario Using BPM .
I have configured every thing using BPM and mapped
MATMAS----SOAP Request
SOAP Resp----STATUS.SYSTAT01
In R/3 the Main Idoc Number(MATMAS) Status needs to be update , but it is creating the new Idoc with STATUS.SYSTAT01.
I have used STATUS.SYSTAT01 Idoc to Update the status of the Original idoc based on the Response that is coming from webservice .
I was posted the same thread a days ago and there Bhavesh suggested me some sugessions.
How can we make the status of the Idoc based on some response Text
iam unable to follow OR not able to clear my self on this.
Please suggest me or give some over view kind of thing on this
Regards

Hi Suman,
It is clearly mentioned in SAP help that "SAP Intermediate Documents (IDOCS) are EDI like documents that are asynchronous in nature."
So Your Scenario is Asynch(receive) - Synch(WS call) -Transformation (Multimapping)- Asynch(Send to R/3).
now go in this way:
you can develop all the message Interfaces of Abstract catagory (not manditory )
MI_AA_MATMAS -> Abstract Asynchronous message interface for your Matmas IDOC
MI_AS_SOAP_ReqandResp -> Abstarct Syncronous MI for SOAP request and response.
MI_AA_STATUS ->Abstract Asyncronous MI for Status Idoc
MI_AA_SOAP_Req -> Abstarct Asyncronous MI for SOAP request .
MI_AA_SOAP_Res -> Abstarct Asyncronous MI for SOAP response .
Thats all in Message interface.
your first reciever :
(This will receive the message asynchronously from R/3)
create a conatainer varaiable (say preceive) and assign it message interface MI_AA_MATMAS
Now in thw Propert TAB of this step: give this message name.
Step2: Synchronous call :
create container Variable psoaprequest and psoapresponse give abstract message interface MI_AA_SOAP_Req and MI_AA_SOAP_Req resp.
Now in thw Propert TAB of this step:
Synchronous Interface : MI_AS_SOAP_ReqandResp
Request Message : psoaprequest
Response Message: psoapresponse
Transformation Step :
Here you will specify Interface Mapping that will conatain Multimapping between Synch Response - MATMAs and STATUS
Let's name it as IM_ResandMatmasToStatus
create a container variable as pstatus and assign it abstract interface MI_AA_STATUS.
In Property pan of this step :
Interface mapping :IM_ResandMatmasToStatus
Source Message :psoapresponse
preceive
(IT will ask you for two source messages as IM selected in this transformation has 2 source messages)
Target Message :pstatus
Send step:
Select a message as pstatus.
thats all in IR.
If have doubt in ID just let me know.
Thanks
Sunil Singh

How to find out the inbound function module in the extended idoc

Hi,
how to find out the inbound function module in the extended idocs
Thanks .

through we41/we42 you can find the inbound function module.......
or
thorough we19(idoc test tool) ....
give the input as message type or basic idoc..
press exec...
then you can find th button on application tool bar as inbound funtion module....
from here also you can find..........
<REMOVED BY MODERATOR>
Khasimsa
Edited by: Alvaro Tejada Galindo on Apr 14, 2008 1:34 PM

Creating Delivery based on the Inbound IDOC received.

Hi all,
I have a requirement where in, Outbound Delivery for Sales order is to be created based on the inbound IDOC received from a third party. The standard idoc type DELIVERY03, requires the Delivery Number for updating the order but it cannot create a delivery number.
Can any one suggest which IDOC type can be used for this or if there is any alternative solution?

Hi,
You can use FM IDOC_INBOUND_WRITE_TO_DB to create an inbound IDoc.
CALL FUNCTION 'IDOC_INBOUND_WRITE_TO_DB'
    EXPORTING
      PI_STATUS_MESSAGE       = I_EDIDS
    IMPORTING
      PE_IDOC_NUMBER          = DOCNUM
      PE_STATE_OF_PROCESSING = STPROC
      PE_INBOUND_PROCESS_DATA = I_TEDE2
    TABLES
      T_DATA_RECORDS          = I_EDIDD
    CHANGING
      PC_CONTROL_RECORD       = I_EDIDC
    EXCEPTIONS
      IDOC_NOT_SAVED          = 1
      OTHERS                  = 2.
Check the following link:
http://www.sapbrain.com/TUTORIALS/TECHNICAL/IDOC_tutorial.html
<b>Reward points</b>
Regards

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,
Amar

Example 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!'.

What are the standard IDOC's available in IDES? where can i see in IDES?

Dear All,
Can any body let me know what are the standard IDOC's available in IDES? What is the path for the same?
Thanks in advance for replies
regards
srikanth

Hi,
IDOCs are intermediatery Documents, we can check for IDOCS using Tcode
WE01 : Create IDOC
WE02 : Display IDOC
WE19 : Reprocess IDOC
etc
Thanks
Kalyan

Issue with the CREMDM IDoc

Hi,
I am sending the Vendor data from ECC to the external system through XI. I am using the change pointers and the IDocs are generated through BD21. IDocs are generated with no errors and the status '3', but the IDocs are not sent to XI. I checked the SM58 transaction and found the errors. Error Message is "EDISDEF: Port SAPXXX segment defn YSTP1EDY_MDMNR001 in IDoc type CREMDM04". I have created an extension for CREMDM04 and in the outbound Partner Functions I have given both Basic and extension types.
As part of our new requirement I have added couple of fields to the custom segment which was already released and in use. After changing and released the segment, a new segment defnition YSTP1EDY_MDMNR001 is generated.
I googled to find the solution for this issue, everywhere I found that the metadata in XI side should be deleted and reimported it manually in transaction IDX2. We have done this couple of times and are of no luck.
Could anyone please tell is this due to someother issue other than the metadata in XI.
Thanks,
Murali.

SAP ERP
1. do you have "set release" at the new segment and idoctype ?
2. do you have provided the new extension in the partnerprofile we20 ?
SAP XI
1. delete the imported IDoc Object in the integration repository/Service Repository
2. reimport the new IDoc (with extension).
3. check your interface objects (message interface/mappings) that the new extension name is used
4. clear metadata and reimport via idx2
maybe you have to clear the cache.
Regards,
Gordon

How to process the Received Idoc in SAP R/3 ? What to be done ?

Hi All
I am working for file to Idoc scenario.....
Idoc received into SAP R/3 but how to process the Idoc data ?
Such it will store in SAP R/3 DB.....
Clearly
How to Process the received idoc data into SAP R/3 ? (this is for inbound idoc)
I hope any one can help me on the processing steps ?
Waiting for valuable inputs form experts
Regards
Rakesh

rakesh
chec <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660">Sample IDoc</a>
normally, based on the idoc types it will get processed. if it is an idoc with master record it will create appropriate master records or if it based for a transaction it will create one.
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098">https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098</a>

HR-PDC interface: Problems in the file name of the downloaded idoc file

I'm currently busy with the HR-PDC interface to EBI-time recording system. The RFC destination to EBI's quality system is working fine but we are experiencing differences in the idoc file name that we are creating in the EBI path. When we send a request to EBI to upload clocks, an idoc (Message Type: HRCC1REQUPTEVEN and IDOC type: HRCC1REQUPTEVEN01 ) is sent to EBI The file name is HRCC1REQUPTEVEN whereas in a previous implementation file name is HRCC1REQUPTEVEN01. The control record information on the outbound idoc are the similiar in terms message types and idoc types sent through to EBI. Have you ever come across this issue in your previous experiences with SASOL's HR-PDC interface. SAP has not changed the IDOC type HRCC1REQUPTEVEN01 since 1998.

can you please also contact IDM support about it?
* http://www.internetdownloadmanager.com/register/new_faq/main.cgi

Some of the error idocs are not falling into Workflow Inbox

The extract of IDOC list with status 51 from WE02 transaction is not matching with Workflow inbox column "object", some of the idocs which are errored are not showing in the workflow inbox. Here we are in need to get all the errored idocs into the inbox. Please suggest me to proceed further.

Hi Smita,
Thanks for your reply.
I have maintained the suggested role SAP_GRC_SPC_SCHEDULER in backend for an user id and i can able to see a job is getting completed in SM37.
However, the task in the inbox hasnt come yet.Any idea you may have as to how much time it will take for task to come into inbox.Or is that i need to do any more extra task.
Please advice.
Thanks
Ashok S

FM to get IDOC number of the created IDOC

I am creating the idoc using FM -- >MASTER_IDOC_DISTRIBUTE
If Idoc is created successfully I get sy-subrc = 0.
If sy-subrc is 0 .... I need to fetch the Idoc number...
I need a FM that will return the appropriate idoc number...
thanks
Warm regards,
Karen

Hello,
try this FM "IDOC_INBOUND_SINGLE", this returns the IDoc number.
Regards,
Sachinkumar Mehta

Enhancements to the INTERNAL_ORDER01 Idoc

Similar Messages

Maybe you are looking for