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

Similar Messages

HRMD_A Inbound Idoc with process Code:HRMD not updated in SAP

Dear friends,
I'm facing a problem with Personnel data creation in SAP (this is not a SAP HR system).
I have a data file with Personnel data, in WE19, I use idoc_input_hrmd to process the data (with basic type: hrmd_a06). Idoc has been created with status '53'. However, when I check in SAP, t-code PA30 with the Personnel number, the record does not exist. Checked infotype tables PA0000, PA0001, PA0002 and PA0003 as well, no luck.
I wonder where does the data go? Is it sitting somewhere in the system and waiting to be processed?
Please help!!!!!

Hi
Authorizations might be one of the reason.
So IDOC transfered but no records to be writeen to DB.
regards
vijay

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

Inbound IDOC error - status code 52- application document not fully posted

Hi,
In Inbound IDOC, the status code is 52 ---> Application document is not fully posted(satus of the inbound idoc is in yello colour). I want to reprocess this idoc in BD87 t.code in order to convert the yellow colour to green colour. Before reprocessing the IDOC, i need to rectify the problem and then reprocess the idoc in bd87. am i correct? if yes, what i need to do to solve the error --->application document not fully posted. Please guide me friends.
Thanks in advance.
Regards,
Sri

HI
If you are FM to process the inbound IDOC,
possibilities are like below .
Reason 1 :
In partner profiles, check is it trigger immediately or not ? for particular partner profile which u r using .
reason 2 :
If you are using BDC code to update the data .if any screen contains error then also you will get the status in yellow .
reason 3 :
Have you tried with TCODE BD87 , might be it is processing error also .
i have worked on same probelm so if u r not solved with the issue after trying above 3 reasons .
reply me back .

Inbound idoc with error status 52 messege type hrmd_a07

i have an inbound idoc with status 52
error messege : Object 01 ,P ,00056786 does not exist: infotype 0302 cannot be created
Object 01 ,P ,00056786 does not exist: infotype 0006 cannot be created
i debugged but i haven't find out the reason
am updating 0000,0001,0002,0003,0006 infotypes

Hi rahul,
Need to check the address filed (0006) for BP mapped to postion (00056786)
Infotype 0302 (Additional Actions) :
Infotype 0302 is not maintained directly and is automatically updated by Infotype 0000 .
The additional actions Infotype (0302) is of time constraint 3 (gaps and overlaps).
Specifically in some cases if we want to have a non status-changing Action on the same day where already a personnel action is existing at that time we can activate the Infotype 302 by executing Report RPUEVSUP.
please check and let me know . I think it will be helpfull
Thanks and Regards,
Krishna

Inbound idocs with flat file

Hi
Iam creating INBOUND IDOCS from flat file ...so my sending and recieving systems are same...
In WE20 i have setup the logical system and assigned inbound parameters with message type and proces code.
Iam using IDOC_INBOUND_ASYNCHRONOUS to create the inbound IDOCS but iam getting the error
EDI: Partner profile inbound not available
It looks like iam missing some settings here..
Please let me know what checks i need to make sure to get rid of this error and post the idoc.
Thanks
Govi

Hello,
You need to create partner profile in WE20 transaction code.
For more details follow the link: [creating PARTNER PROFILE|http://help.sap.com/saphelp_nw04/helpdata/en/2d/f371e4d24a11d289810000e8216438/frameset.htm].
Hope this resolves your issue!
Thanks,
Augustin.

How to Test, Inbound idoc ,with out the Sender System, using a Text File

Hi Guru's .
we wanted to test BLAORD03 inbound idoc (Message Type BLAORD).with out the SENDER SYSTEM.
on the same client.
we wanted to test this idoc with text file from our local machine.
Can anyone give us detail steps.like how to create File layout
with Segment name,and values for the fields.how to pass this file to the system.
Thanks in advance.

Hi Aparna.
My requirement is to test the idoc with Inbound File.
Generate a file with the data entered through segments through we19 ,and use the same file for processing through we16.
when i am trying to do this syst complaing about
Partner Profile not available, and some times
port not available. and some times with
'No further processing defined'.
but i maintained part profiles and port perfectly.
Can you help me in testing with test 'File' port.

Inbound IDOC with UNICODE issues

We are trying to send in an IDOC with Romanian characters that are outside of latin-1. We have upgraded our 4.7 SAP system to be UNICODE, but when loading these characters via IDOC they are not being represented correctly in R/3. We have tried setting our login language to RO when doing the input and it doesn't seem to matter. Is there a setting somewhere that we are missing to designate an inbound IDOC as UTF-8?
TIA...
Darrin

Hi Darrin,
if the sender of the IDOC is an external RFC program, you should use the "Codepage" parameter in the logon string, to declare your character set. The SAP RFC lib will then translate between external and R/3 internal codepage.
If you find my answer useful, please don't forget the reward.
Regards,
Juergen

Inbound Idoc With LSMW

Hi All
We are creating transactions for legacy data migration with LSMW using inbound Idoc. We are able to do the same successfully. As per requirement for each transaction some word and Pdf files have to be attached. Is there any way to attach documents with Idoc through LSMW?
Thanks
Avi

Hi Avineesh,
What you can do is use two LSMW.
First one to upload transaction data and get the transaction number of all the uploaded transactions using IDOC.
Secondly use LSMW with BDC to attach the files to that specific transaction.
Or
In option to above approach you can use LSMW with BDC to upload all the transaction along with attachment.
Best Regards,
Pratik Patel
<b>Reward with Points</b>

Issue with UPC codes in Inbound sales orders via EDI.

Hi All
We are on ECC 6.0. We have incoming sales orders through EDI IDOCS. In the incoming IDCO the customer can provide either of the following information in that sequence.
1. GTIN number
2. Customer material number
3. UPC code
4. Old Product code.
We need to derive the correct material number for each customer. Now I can achieve this through standard material determination using material determination type access sequences in the order specified above. However I cannot do the same, as we need to use material determination for genuine promotions. For example I can maintain a material determination record to map UPC 123456789 to Material number ABC in SAP R/3. However we do have situation where in for a particular season or depending upon the ATP situation we may have to derive Material XYZ (SAP material number) in case customer orders material ABC. So in other words if I use material determination to derive my SAP material number for in-coming IDOCS based on UPC codes then I would need to have multi level material determination. I.e. From an IDOC for UPC code 1234566789 I derive material ABC and then for material ABC derive material XYZ.
I tried setting up these two layers of material determination in the standard system. It is possible only if I use a substitution reason which copies the material entered as a sub-item. We do not want to maintain the sub-item in sales order and relevant documents for a lot of other reasons. Is there a way I can use standard Material determination/substitution to derive this multi level search without haveing to copy the sub-item in sales order? Am I missing some settings here? If not is it possiblt to suppress the sub item from being derived in SAP using some user exit in sales order processing?
For an IDOC I could have used standard SAP tables to identify SAP material number based on UPC code. However the problem is we have multiple SAP material numbers assigned to one UPC code. So it is not possible to identify a unique material number just based on the UPC code.
I would like to know if any of you experts have encountered a similar situation and if so what is the ideal way to resolve this issue. Any comments/suggestions/guidance is welcome. You can also reply at my e-mail id [email protected].
Thanks

Hi Daniel,
Can you please which IDoc message type you are using to create sales order using IDoc?
Also check in IDoc, what is the value of ACTION & EINKZ fields in segment E1EDP01?
Regards,
Amit

ALE IDOC with T-code :IE01

How is an ALE IDOC generated when an equipment is created with T-code :IE01

Hi K.R.,
First of all you need to check if everyting works fine.
For this specific IDoc you can check table T705Z with KANAL='2' and AKTIO='4' and with DATUM=<Date of receiving IDoc>. You can also use UZEIT as a filter here.
Why?
At the moment this IDoc (CONF21) comes inbound to SAP, through the process code CON2 it actually must start function module KK2A_GET_DATA_FROM_IDOC. This places the entry and you can then see that your function has been called.
Secondly inside function module KK2A_GET_DATA_FROM_IDOC the process for updating is started in a parallel (asynchronous) process. Actually function module PROCESS_CC2_MESSAGES_PARALLEL is triggered as a background task that controls its own parallel processing. On its turn this calls the logic in function module PLANT_DATA_ANALYZE_PARALLEL and therein the function module PROCESS_CC234_MESSAGES.
With these mentioned function modules a table is preserved (named ET_PROT) and this table contains (internally) any message, so also error message text.
Unfortunately you are not able to get to this internal table if the proces is running in the background.
Now when SAP calls the parallel process (in background), programcontrol is returned immediately. So function module KK2A_GET_DATA_FROM_IDOC can then finish. Finishing here without setting any error status will lead to final status 53 for the inbound IDoc.
And as you can imagine, it does NOT wait for the result of the background process. Therefore status 53 represents only the fact that function module KK2A_GET_DATA_FROM_IDOC has runned without errors. It does not report errors possibly occuring in PROCESS_CC2_MESSAGES_PARALLEL.
Now how is this then to be solved?
You need to create your own data for running the above mention logic, preferrably based on failed IDoc data and then debug the whole thing (to find the error).
Hope this helps you a bit on your way,
Regards,
Rob.

Idoc at status 51, however outbound delivery created

Hi Gurus,
We have peculiar issue , where in outbound delivery is getting created through IDoc. The inbound idoc has status 51 however delivery got created. Any idea how is it possible?.
Thanks in advance.

Dear Math,
Have you got the solution for the above. If you get can you tell me please because even i got the same error message while processing the IDOC
status 51 after status 53. Outbound delivery is updated but not the sales order.
can you please help me

WE-19 Inbound Idoc Process - Status Code 51

Hi,
I generated Outbound idoc COND_A successfully to send it out to XI. I used same Idoc again in WE19 and changed partner details and tried Inbound Processing. Its giving me error code 51 ("ISO Currency USD can not be converted unambiguously to SAP currency for E1KOMG" )
Any Idea how to fix this error. basically I did not changed anything.
Message was edited by: Ram Krish

Appana,
Thank you very much for your reply.
I did setup all parameters as Iam getting this Idoc as an Inbound to R3 as well. Thsi Idoc will be both Outbound and Inbound to R3.
I successfully sent this Idoc to XI. and then as I wanted to test the same Idoc for inbound, I changed Paramters according to my setup.
Sequence of status are
74 - created with test transaction
50 - Idoc added
64 - Idoc ready to be transferred to Application
62 - Idoc Passed to Application
51 - ISO currency USD can not be converted unambiguously to SAP currency for KOMG
I looked at several fields in E1KOMG segment and changed one of the currency field to USD which didn't help to fix this error.
I really appreciate any help to fix this error.

How to edit inbound idoc with data errors in multiple segments and reproces

Hi friends,
i have a requirement for error handling of inbound sales order(ORDERS04) without using WORKFLOW and WE19.
i have seen some function modules like edic_* ..
but my doubt is how to edit the error data(how can i identify the particular error fileds in the segments)and how to reprocess the same idoc.
Please help me...
Thanks in advance

Hi Narasimh,
Please find the following steps to edit IDOC segment after you find the error using WE02.
The example codes can be found in website
http://www.sapgenie.com/sapedi/idoc_abap.htm
STEP 1 - Open document to edit
CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
       EXPORTING
            document_number               = t_docnum
       IMPORTING
            idoc_control                  = itab_edidc
       TABLES
            idoc_data                     = itab_edidd
       EXCEPTIONS
            document_foreign_lock         = 1
            document_not_exist            = 2
            document_not_open             = 3
            status_is_unable_for_changing = 4
            OTHERS                        = 5.
STEP 2 - Loop at itab_edidd and change data
LOOP AT itab_edidd WHERE segnam = 'E1EDKA1'.
e1edka1 = itab_edidd-sdata.
IF e1edka1-parvw = 'LF'.
    e1edka1-partn = t_eikto.
    itab_edidd-sdata = e1edka1.
    MODIFY itab_edidd.
    EXIT.
ENDIF.
ENDLOOP.
STEP 3 - Change data segments
CALL FUNCTION 'EDI_CHANGE_DATA_SEGMENTS'
           TABLES
                idoc_changed_data_range = itab_edidd
           EXCEPTIONS
                idoc_not_open           = 1
                data_record_not_exist   = 2
                 OTHERS                  = 3.
STEP 3a - Change control record
CALL FUNCTION 'EDI_CHANGE_CONTROL_RECORD'
       EXPORTING
            idoc_changed_control         = itab_edidc
       EXCEPTIONS
            idoc_not_open                = 1
            direction_change_not_allowed = 2
            OTHERS                       = 3.
STEP 4 - Close Idoc
Update IDoc status
CLEAR t_itab_edids40.
t_itab_edids40-docnum      = t_docnum.
t_itab_edids40-status      = '51'.
t_itab_edids40-repid       = sy-repid.
t_itab_edids40-tabnam      = 'EDI_DS'.
t_itab_edids40-mandt       = sy-mandt.
t_itab_edids40-stamqu      = 'SAP'.
t_itab_edids40-stamid      = 'B1'.
t_itab_edids40-stamno      = '999'.
t_itab_edids40-stapa1      = 'Sold to changed to '.
t_itab_edids40-stapa2      = t_new_kunnr.
t_itab_edids40-logdat      = sy-datum.
t_itab_edids40-logtim      = sy-uzeit.
APPEND t_itab_edids40.
CALL FUNCTION 'EDI_DOCUMENT_CLOSE_EDIT'
       EXPORTING
            document_number = t_docnum
            do_commit        = 'X'
            do_update        = 'X'
            write_all_status = 'X'
       TABLES
            status_records   = t_itab_edids40
       EXCEPTIONS
            idoc_not_open    = 1
            db_error         = 2
            OTHERS           = 3.
Hope this will help.
Regards,
Ferry Lianto

File to IDOC:how do i relate inbound idoc with generated idoc in the R/3

hi experts;
can any body tell me how can i relate the IDOC number genrated in the PI with the generated IDoc number in the SAP R/3 system for file to IDOC scenario?
in SAP PI for tcade idx5, idoc no is:12002
but in SAP R/3 in tcode WE05, idoc no is:846915
how can i know a particular message (in SAP PI) created a particular idoc in the backend SAP R/3 System.
thanks in advance,
kumar

Hi Kumar
at the time of testing you have to note down a time at what ur file got picked up ok
then go to we05
-> give the date on CREATED ON field.
-> then in BASIC TYPE field select your particular IDOC CREMAS05 or whatever, see the TIME field that you have noted down at the time of testing, if that is matching means that is ur latest IDOC you have tested.
-> one more thing, tha last IDOC showing in the list means that is your latest IDOC you have tested.
Hope i have helped you, points plz
Warm Regards
Dheeraj Kumar

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

Similar Messages

Maybe you are looking for