Confirm Inbound IDOC FM

Hi,
Please confirm whether this FM can be used to post the inbound cycle count.
L_IDOC_INPUT_WMINVE
Let me know whether it relates to li11n transaction.
Regards,
B.Anandh

Yes to both.

Similar Messages

Enhancement for picking confirmation inbound idoc

Hi Friends,
I'm using Message type SHPCON , Basic Type Delvry03 and process code DELV for picking confirmation. where as i have to extend the basic type for a field LIPS-UECHA ( Batch split Indicator) which is not avilable in basic type. which userexit or badi i have to use to plopoualte this filed data in to SAP? Can any one help.
Thanks&Regards,
Naren.

Hi,
You exttend the basic IDOC type DELVRY03. To which Segment you want to add this under E1EDL24 or E1EDL37. Change the process code inorder to fetch the data from the application.
WE31 to add the field to the segments and create a new segment
WE30 extend the basic type and add the newly created segment
WE82 to add the extended basic type to Message type.
change the process code.
Regards
Kannaiah

Inbound idoc for updating delivery date of purchase order

Hi All,
Our vendor sends a delivery file consisting of delivery date and quantity(could be partial) for line items of a purchase order.
I need to update the Purchase order line item with the delivery date and quantity sent from the Vendor. It should add a new confirmation line with custom confirmation category in the confirmation tab of the line item in the Purchase order.
Each time we get a delivery file we need to add a new confirmation line in the confirmation tab of the purchase order line item.
How can I get this working using inbound idoc processing? Which Idoc type should I use to solve my issue. Will ORDERSP work for my scenario?
Thank you,
Sonali.

>
sonali ashi wrote:
> We have all EDI set up done for ORDERSP idoc in our system. Problem when I use this idoc type by default system is always adding confirmation catgeory 'AB' but we want our custom category to be added instead of 'AB'.
> Edited by: sonali ashi on Dec 23, 2010 9:47 PM
Confirmation category used for order acknowledgement is define in configuation. You can change that from AB to your custom condition and EDI should pickup that.
SPRO->Material Management->Purchasing->Confirmation->Define Internal Confirmation Category
>
sonali ashi wrote:
> I have also noticed that 'AB' confirmation accepts only full quantity order acknowledgement through Idoc processing.
> Manually I can add a "AB" confirmation for partial quantity but in the idoc processing it fails.
> Edited by: sonali ashi on Dec 23, 2010 9:47 PM
Check tolerance limit defined for confirmation category in 'Conformation Control' Node in SPRO at same level as above.
Regards,
Pawan.

Inbound Idoc with T-code: BORGR ( Inbound delivery create) EDI cannection

Dear all,
Kindly help me to create inbound delivery with BORGR transaction.
Here the we have to create the inbound delivery in the system with the help of vendor number and material without using Scheduling agreement number in BORGR
Please suggest the processing code and the function module required for the BORGR document posting.
I have done the following steps u2026but not able to post the dummy idoc through WE19 .
1.     Use standard message Type DESADV (T code: WE81).
2.     Use standard IDOC type DELVRY05 (T code: WE30).
3.     Assign message type to IDOC Type ( Tcode: WE82).Message Type:-DESADV, Basic Type:-DELVRY05,Release 700
4.     Use standard assignment of process code DELS with the message type DESADV ( Tcode: WE42)
5.     Inbound Function Module : IDOC_INPUT_DESADV1 ( T code : WE57)
6.     Define Port type File (Tcode: WE21) Port u2013 EDI_ASN Inbound Delivery.
7.      Define Partner Profile (Tcode: WE20) Inbound Parameters.
8.     Enhancement can be done in inbound IDOC as per the business requirement. Business has confirmed Field name wise Inbound IDOC data which will be received from vendor and all fields are available in the standard IDOC type DELVRY05.
Please help if anything more required for posting dummy idoc .
Thanks and regards,
koshti

Hi Dick,
just one additional hint as we had recently such problems :
It my happen that DESADV creates an inb.del <b>w/o</b> packing the HUs (idoc status is 'yellow' instead of 'red'). To avoid this OSS #912470 is the solution.
Kind Regards
Kay

Creation of a line item in the existing PO by inbound idoc (ORDERS05)

Hi friends,
I have the following requirement.This is for the inbound idoc ( orders05).
If there is an extra item line in the confirmation idoc, for which no corresponding purchase order line is found, check if the extra line's NOB-number is found in the new NOB-number check -table.
Fetch NOB-number check table with database keys:
E1EDP19-IDTNR (when E1EDP19-QUALF = ZNO) = NOB-number in the table
EKPO-WERKS (from 1st purchase order item line) = site number in the table.
If the NOB-number + WERKS is found in the control table, create a new item line in the purchase order.
If the NOB-number + WERKS is not found in the control table, put the idoc into error.
Can you please tell me that how to create a new item line in the purchase order.
Waiting for your help.
With Regards,
Ajit Prasad.

You like to add new line item in existing purchase order or new po.
Thanks,
Narayan

Message variant is missing in INBOUND IDOC.

hi,
Any one can help on this issue?
The sender has confirmed that message variant was filled in outgoing file.
However, When we received this Inbound IDOC, the message variant is blank.
I still am confused by two questions:
1. The function module which insert record into table EDIDC and EDIDD, is same as the function module which post this IDOC to sap module(normally we maintained it in WE57)
2. We normally need to maintained in WE57, but also need create one processing code, what is relationship between WE57 and processing code(WE42)

Hi,
Message Type/Message Variant needs to be maintained in WE20 ( Partner Profiles). In case of inbound IDOC ( receiving the data other systems) Data processing/posting will happens via function module. the function module will attach to the process code.
Process Code : The IDoc interface uses the process code to find the business process which controls the conversion of the IDoc into the SAP document.
The Process code will assign to the function module in WE42, the same function module will assign to the Message type and Idoc type in WE57
In a short summary, The Function module required to post the Idoc/update the data in SAP. However the Function module should process specific to the Message type and Idoc type only. It means the settings is required to identrify the correct function module to process the Inbound Idocs.
Whenever there is a problem with ALE setting the message 64 will trigger, it means the IDOC is ready to transfer to the application ( process through FM ).
Thanks,
Kiran.

Problem with HR inbound IDoc

Hi,
I have a problem with processing inbound IDocs from an external payroll system to infotype 0008. The process is quite simple; salary changes from the payroll system is recorded to the corresponding employee's infotype 0008. When testing I noticed that that the new record is recorded as is. For example if there is already an existing record with the validity dates 01.01.2010 - 31.12.9999 and the new record in the IDoc is 01.01.2011 - 31.12.9999, the new record is written as is. I would expect the system to delimit the old record correctly - similar to what would happen if you maintain records online. There is no error checking or any kind of processing done by the system.
I did some debugging and found out that the function module linked to process code HRMD writes the information directly to the database. If this is a standard way of doing this, it is really unusual.
Has anybody else encountered this? Any pointers?
Thanks.
Edited by: Theo Droste on Jan 20, 2011 11:56 AM

Hi
This is correct, the ale programme writes the data directly to the database, I have faced this isssue on occassion. I once raised an oss message on this as well, and sap confirms this is what happens. If it is a sap to sap ale, it somehow seems to work, - this could be because the outgoing idocs are created by sap itself but if it is a non sap to sap ale the onus is on us to ensure that the external system sends the correct data to sap in the way we intend it to be displayed.
that is how it has been in my experience. It is unusual, but apparently not impossible. Please let us know if you find out anything different.

Confirmation TO IDOC WMTCID03

Hi ,
This IDOC is used for confirmation that comes from external syste. SAP confirms the TO in the background. SAP confirms that based on the function module.. my question is what are minimum fields that SAP should have inorder to confirm the Transfer Order?
can it only confirm if it received TO number and Item number from external system ? if yes how we can test it ?
Thanks
Rahul

Dear Manish,
I do think that my post adds value since I had the same issue. I wanted to test inbound IDOC WMTOCO but kept running into an error (Idoc was posted successfully, but the confirmation did not take place).
After spending some time searching for this issue on the net, I debugged the standard code and found that the confirmation did not take place because the TO wasn't sent to an external system.
This is the question that was asked in the main topic "can it only confirm if it received TO number and Item number from external system? If yes, how can we test it", but wasn't answered by Gopinatha Rao Ganesh Kumar.
I hope that with my message I will help other people who have this issue and will search on SCN (just like I did, but didn't found any answer). If they have further questions, they can always reply the message.
Thank you,
Rens

Inbound IDOC receiver port not getting filled in

Hi All,
I checked the WE20 configuration and it is fine. Just wanted to check if there is any other sap configuration which might be missing.
The IDOC is coming from a web server and they confirmed that they are filling the receiver port information while sending, but in the IDOC that we receive in SAP the receiver port is coming as blank.
Any pointers will be appreciated.
Thanks,
Anil

Hello Anil,
When they say they are filling receiver port that means they filling EDIDC-RCVPRT, please note with out receiver port you will not be able to receive the Idoc.
It means this value might be cleared somewhere in SAP. may be user exit or BADI or enhancement. what you can do is try to create inbound idocs by populating receiver port using WE19 and check whether the created idoc contains this value or not.By doing the you can get an idea where this value is disappered.

Inbound idoc ordsp fm:IDOC_OUTPUT_ORDRSP

my problem is that idoc fails when it comes in as a response of ORDCHG when user changes the delivery date in PO outbound idoc triggers with message type ORDCHG. Vendor sends the response as a confirmation of order via inbound idoc message type ORDRSP. it fails at that movement and gives an error ME 790(material number differ from .............) it is comparing the value of segment E1EDP19 qualifier 001 field IDTNR with ekpo-matnr &ekpo-ematn.
NOTE: there is value in segment and it is correct value. but when inbound idoc fails it is taking blank value in fekpo and comparing with ekpo-matnr &ekpo-ematn and giving an error ME 790
and when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully
one more thing i noticed in all failed idoc that segment E1EDK02 qualifier 002 not got populated which contains vendor acknowledgement number.
but when we reprocess it in WE19 without doing any changes it posted sucessfully.
thanks in advance.

You say that "when we reprocess the same failed idoc without any changes in it via WE19 it posted successfully". What about if you reprocess the same iDoc via BD87 ? If you are using the same Function Module, this shouldn't happen, unless you have some very specific userexit code around the user or transaction type.
Cheers, Paul.

Enhancement for inbound idoc posting(idoc_input_ordrsp)

hi,
please find solution for the below.
business senario: when the vendor send purchase order confirmation through idoc a automated acknowledgement has to be send.
technical: when vendor send idoc (orders05) it updates with FM (idoc_input_ordrsp) our system.
but in the idoc a segment E1EDP19 will have the field IDNLF which has to be filled to send a acknowledgement .
in my case:
the user some times will fill the segment so to get automated acknowledgement we have to write an enhacement to populate the segment in inbound FM.
i have written code in EXIT_SAPLEINM_007. and populated the data in internal table. but the changed data in internal table is not reflecting in processed idoc(in we02 direction 2).

idoc_data is the intenal table which hold all the segment data in run time.
now i fetched matnr from ekpo table populated E1EDP19
and modified the internal table by adding idoc_data-sdata when idoc_data-segnam is E1EDP19 .
ultimately the sdata is reflecting in the idoc_data-sdata for the segment.
but when we check in we02 for the processed idoc the changes are reflecting.
give me a solution for the data to reflect in processed idoc.

Converting Inbound idoc to Outbound idoc

Hii,,
How to convert inbound idoc to outbound idoc.
I have IDOC -> SOAP -> IDOC Scenario.
In case of error at SOAP side , it return idoc with 51 status.
Now i need to convert the Inbound idocs to Outbound Idocs and send it back to the Sender system...
How to do accomplish this??
Regards,
Siya

Hii,
By using we19 and by exchanging sender & receiver we can convert outbound idoc to inbound idoc.
Just want to confirm is it proper way??
Regards,
Siya

Process of inbound idoc

Hi,
can any one pls let me know the steps we should fallow in an inbound idoc processing.
I have the messagte type , basic type, process code and i have to create partner profile , pls let me know what are the steps to be fallowed
thanks,
Deepak

Hi,
U need to update the Purchase Order based on the idoc.
The Process Code for this development is: ORDR,
Basic IDOC Type: ORDERS05
Function Module: IDOC_INPUT_ORDRSP,
Message type: ORDRSP.
Enhancement: MM06E001
Customer Enhancement: EXIT_SAPLEINM_008
The logic should be written in the Include ZXM06U20.
LOOP AT idoc_data.
CASE idoc_data-segnam.
WHEN 'E1EDP01'.
Move Structure ACKNOW_PO info to Confirmations.
ENDCASE.
ENDLOOP.
Regards
Kannaiah

Forward Inbound - IDOC process

Has anyone used this option WE45- forward Inbound for inbound IDOC automatic processing?
<b> The help says
"Specify a job as a logical address for forwarding the data from an inbound IDoc or from a status confirmation".</b> But need more details if anyone has used. We are looking for internal invoice posting in application V3 .

INBOUND_IDOC_PROCESS is the function module to be used before release SAP R/3 4.0; since release 4.0 you should use IDOC_INBOUND_ASYNCHRONOUS instead.
Similarly as indicated by the previous posting IDOC_INBOUND_SINGLE replaces function module IDOC_INBOUND_SYNCHRONOUS for posting a single IDoc.
Best wishes, harald

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.

Confirm Inbound IDOC FM

Similar Messages

Maybe you are looking for