DELV process code triggers unwanted inbound idoc!

Hi,
I am creating a delvry03 idoc with message type shpord.The process code is DELV.I am sending the idoc from LS to KU.I maintained the outbound parameters in both receiving and sender systems.The outbound is creating perfect.However, there is an unwanted inbound idoc that is being created.All the inbound idocs getting created in this way is in error.I am not able to understand why the inbound idoc is getting created.
I see DELV as both outbound and inbound process codes, but then i am not able to understnad why shpord message type is getting processed.I have not done the distribution model as the receiving system is customer.
Could someone help me out in this weird scenario.Thanks

Duplicate in ABAP General deleted. Post in ONE forum only, please.
matt

Similar Messages

How to write processing code for the Inbound IDOC to the R/3 ??

i m having a file -> XI-->R/3 scenario,
IDOC is being sent from XI to R/3,
can u guide to me to write a processing code for the Inbound IDOC to the R/3,
since i m new to ABAP and ALE technology, can we provide me any blog for doing that.......or guide me....

Hi Sudeep
Simple File to Idoc scenarion blog
/people/ravikumar.allampallam/blog/2005/06/24/convert-any-flat-file-to-any-idoc-java-mapping - Any flat file to any Idoc
Also see the blog
<a href="/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi Steps for Posting IDOC's</a> by Ravikumar.
Configuration of IDOC adapter
http://help.sap.com/saphelp_nw04/helpdata/en/96/791c42375d5033e10000000a155106/frameset.htm
Regards
Santhosh
*Reward points if useful*

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
Anil

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

Need of Process code in ALE Inbound Processing?

Hi All,
What is the need of process code in ALE Inbound Processing? Why do we need to reach the function module through process code? we can as well directly point to function module.

Hi Ravi,
Please chcek this link perhaps it may help.
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b804043d711d1893e0000e8323c4f/frameset.htm
Regards,
Ferry Lianto

Workflow to be triggered if Inbound Idoc is successful

Hi,
Kindly help me out with the following senario:
After the vendors are created in MDM, they are distributed to an R/3 (ECC 5.0) system via XI. XI uses the message type CREMAS to distribute the vendors. When the inbound Idoc is successsful, a workflow should be triggered to the concerned user about the vendors created in the R/3 system.
How can we find out which event gets triggered when the Idocs were successful such that we can trigger a custom/standard workflow??
Thanks in advance
Regards
Kishan

This report might help you
RSEIDOCM
Otherwise maybe in ALE customising you could create an event in a user program and use FM SAP_WAPI_START_WORKFLOW to launch your workflow.
You will have the IDOC message types coming in and the process codes which are executed so you should be able to monitor the process and take whatever action you need during the process..
(Customising -- use transaction SALE)
cheers
jimbo

Urgent help required : Batch processing error of an inbound idoc

hi,
i have a problem while posting an idoc to the GL(FB01).
i'm using an Inbound idoc message type : ACC_GL_POSTING
idoc type : ACC_GL_POSTING01.
Process code : BAPI.
In the transaction code OBA7 i have enabled a particular document type as BATCH INPUT ONLY.
i have set the option " Trigger by background program" in the partner profile (we20).
while testing the process i'm getting the error "Document type -- is only defined for batch input".
how can i overcome this error? can idocs be used to post for transaction that are batch enabled . plz help me.
with regards.
T.Jeyagopi.

Jeyagopi,
There are different types of Data loading into SAP.
BATCH INPUT / BDC / IDOC / BAPI etc. BATCH INPUT are standard programs that take the data and update SAP. I don't think that is same as batch processing of IDOC.
You might want to remove the setting of batch input, retain the batch processing in WE20 and try it out.
In my opinion it should work.
Regards,
Ravi
Note : Please reward points for the posts that help you.

Wrong processing code used in inbound processing

Hi
We are on 4.6C and have configured a dist. model for material distribution using message type MATMAS. On receiving end IDOC is properly received but processed with code 51 which is "IDOC Interface not complete for message type".
While testing it in we19 with standard inbound option we found that its using process code AFSA though in the inbound partner profile its set to MATM. (In the table tbd52 AFSA is not even defiend for MATMAS but for ARTMAS) While using INBOUND FM option there with FM specified as IDOC_INPUT_MATMAS_MDM we were able to process the IDOC properly in receiving end. We are not sure which code is being defaulted to during automatic inbound processing but we guess its same as AFSA as shown during standard inbound option. It will be of great help if someone can explain what might have gone wrong.

Dear Renjith
I got it. Actually the process code was correctly attached in sending system but in receiving system it was unfortunately set to AFSA which I ignored. Thanks a lot for the response.
regards
saurav

Process code or Fmodule for Idoc type PREQCR101 and message type PREQCR1

hi all,
Iam unable to find the process code or function module for the idoc type PREQCR101 and message type PREQCR1 for inbound process.
help from some one would be a lot appretiated.

Hi,
Go to transaction WE57 and you can find the processing FM and message type that are associcated to the IDOC type.
For process code if it is Inbound check WE42 and outbound check WE41 transactions
Regards
Shiva

Why there is need to define processing code (we41/we42) in Idocs?

Hi All,
Why there is need to define the processing codes when we already have defined the processing function for the IDOC type & message type combinations via we57.

Hi,
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b804043d711d1893e0000e8323c4f/content.htm
The inbound function module needs to be linked to the message type and the mess type needs to b linked to the appropriate process code at the partner oprofile level before any scenario is enabled.
Regards,
Gayathri

Why dont we need process code for outbound master idoc?

For inbound master idoc we need a process code (EX. matmas03-MATM) but for <b>outbound master idoc</b> why dont we need process code?can anybody clarify me on that.
thanx in advance....

plz clarify me on that...its urgent...

Workitem not triggered for Inbound IDOC Error (ORDERS05)

Hi,
The work item is triggered for the Syntax Error in the Idoc (EDI: Partner profile Not Available).
But, as per my requirement i need to get the idoc error status (as Workitem) , any help regarding the resolution of this issue is highly appreciated.
Regards,
Rusidar S.

Hi Uwe,
Many thanks for your response, well i did run the report name that you said me.. when i executed that report i got a workitem as "ALARM Message from Active IDoc Monitoring" and workitem for EDI syntax errors"EDI: Partner profile inbound not available"
But my objective remains unsolved.. i need the error status of idoc to be generated, do u have any idea or solutions, kindly share it as its the 3rd day that am still into the same task....
Regards,
Rusidar S.

With the Z process code IDOC going to status 64

Hello Everyone,
I have created the Z process code for a custom function module via finishing the steps in BD51, WE57 and WE42.
But when I used this Z process code in my inbound idoc, my IDOC are going to the status 64.
Any inputs please?
Thanks,
Pooja

Hi,
Which FM you are calling to post the IDOCs? If you are using IDOC_INBOUND_WRITE_TO_DB or IDOC_INBOUND_ASYNCHRONOUS IDOCs will be posted in 64 status ONLY.
Please call "IDOC_WRITE_START_INBOUND" to post the IDOCs immediately.
Regards,
Ganga

How to assign own Process code to a function module

Hi,
In we42.
How to assign own Process code to a inbound idoc
function module?
Here function module name is not coming in the list.
Ansar.

Hi,
USe transactn: WE42, define ur process code, double click and assign func module...
To know all the transactions for ALE IDOC.. use
WEDI.. Goto SAP easy screen there just type WEDI in command box and enter.
Plz mark if useful..
Regards
Divaakr

Inbound IDOC & Comminication in Nomination

We have a scenario on the Mining industry where we created nomination (T Cd : O4NSN ) for transport of coal by railways . The outbound communication IDOC was successfully sent to a Transport Agency and is reflected in the u201C Communication Tabu201D of the Nomination.
I am getting following issues :
1. Subsequently , the Transporter/railways has send a back a communication via incoming Idoc which fails with following Eror Message : EDI: Partner profile not available
We have tried to create the partner function for processing of Inbound Idoc with following data .
Message type     : OIJ_NOM_COMM
Basic Type     : OIJ_NOM_DETAIL01
Partner Type     : KU
Can you please inform me the approriate Process Code for the inbound IDOC ?
2. Also I have noticed that that During Outbound Communication to the transporter the u201CActionu201D (Communication Tab of Nomination) field idicates as u201C Current Itemu201D. But my understanding is that it should show status : u201C New entry sentu201D .
Can you please guide on how I can define the partner function and resolve these issues .

An inbound IDOC in error will have the status 51, & it is marked for deletion it has a status of 68.
http://www.dataxstream.com/2009/10/mass-status-change-sap-idoc/
http://wiki.sdn.sap.com/wiki/display/ABAP/IDoc+Statuses
Edited by: Krupaji on May 6, 2011 2:38 PM

Message type, Idoc type and process code in ALE/Idoc

Each Idoc version(creams01 or cremas03) will have seperate process codes in Inbound process?
Whether Message type triggers the process code or the Idoctype/idoc triggers the process code in Inbound process?
regards
Message was edited by: henry

Hi Henry,
About your question as how should you assign seperate process code for the same message type ( with different IDoc Type )-
In We42, the message type can be assigned to the processing code. But here you will find that along with message type there are two more fields - Message Code & Message Function.
You can use any one these to serve your purpose.
e.g. you can assign
-process code P1 to message type M with Message code 1
-process code P2 to message type M with Message code 2
Further these process types can be configured to call separate FMs.
Now depending on IDOC types your external system should populate the message type as well as Message code so that accordingly process code will be determined at the time of inbound processing.
I hope it's clear & correct
Thanks,
Ram

DELV process code triggers unwanted inbound idoc!

Similar Messages

Maybe you are looking for