Inbound Idoc set up..

Hi All..
Iam using the following bapi " BAPI_SALESORDER_CREATEFROMDAT2" to create credit/debit memo requests in sap. If the bapi fails, i want to create an idoc and post the application document.
For that purpose, iam using the idoc type SALESORDER_CREATEFROMDAT2 which has the same strucutures as needed for the above bapi. Since the existing message type SALESORDER_CREATEFROMDAT2 is used for other purpose, for my scenarion iam creating a zmessage type. Iam also copying the FM: IDOC_INPUT_SALESORDER_CREATEFR to Z functionmodule to remove the hardcoded value for business object. Iam also creating my own process code.
In this scenario.. iam getting a flat file to SAP. Iam reading the flat file into internal tables and creating the needed internal table for the bapi structurres and passing them to the bapi to create credit/debit memo request. Whenever the bapi fails, i have to pass those structures to the IDoc type to create and idoc and after creation of idoc, it should try to post the application document using the Zfunctionmodule above.
Can you please let me know what are all the settings needed for this Idoc configuration. Also in this case do we need partner profile set up or not.. Where can we set up all those process code, FM, message types etc..
Appreciate your help..

Please refer this thread, it might help:
IDoc FM

Similar Messages

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 used for updating Sales order status

I have a requirements to set use standard IDoc to send out the Sales order to a non-SAP software as well as receiving Inbound IDoc to update the status of sales order in SAP. Could someone comment on my questions below:
1. What are the difference between all the ORDERSxx Idoc types?
2. What IDoc should be used for Inbound IDoc to update the sales order stataus in SAP?
3. Can the same IDoc type be used for both Inbound and Outbound with only the difference in the segment of Direction?
Thank you. Points will be awarded appropriately for helpful comments.

Hi,
1.Intially standard IDOC types "ORDERS01" is having limited
      segments. After few months the requirement got increased to
      add more fields to "ORDERS01".So,once you release the IDOC
      type you can not add any more fields .So SAP come up
      with "ORDERS02" with new fields.Like that all IDocs types have
      some more new seg ments.
2.You can use ORDER05
3. Yes you can use same IDOC type

Updating transaction MD61 using information from inbound IDOC

Is there any standard IDOC type for Planned Independent Requirement(having fields of table PBED and PBIM in its segment)?If such an IDOC type doesnt exist then i have to go for custom idoc type creation
I have an inbound IDOC having 4 fields in its segment
1.SAP Material number
2.Plant
3.Plant Quantity
4.Requirement date
Now i have to use this information in IDOC to update transaction MD61(create a planned order).
constraints:
in MD61 screen1
SCREEN 1
Material radio button is defaulted to on. This must also be set in the interface. Material number will be valued from the input file.
Plant will be valued from the input file.
Version number defaults to 00, so that value should also be used for the interface.
Planning Horizon From and To dates will be the same date and valued from the input file.
Planning Period should be set to D for Day
SCREEN 2
Material number should default from SCREEN 1 input. The interface should also do this.
MRP Area will default from the Plant on SCREEN 1 input. The interface should also do this.
Version will default from the 00 on SCREEN1. If needed on interface, also default to 00.
Version Active checkbox will be checked by default.
Base Unit of Measure will default from material master.
Only a single date column will appear which should be the date input on SCREEN 1. Value this column with the quantity from the input file.
Input fields are highlighted in screenshots below.
After input is complete, use the SAVE icon to store the data.
Kindly tell me the approach to prepare this interface?

Done,used BAPI_REQUIREMENTS_CREATE TO DO SO

Inbound IDOC to post goods receipt with inbound delivery as reference

Kindly let me know the message and IDOC type for
Inbound IDOC to POST GOODS RECEIPT with inbound delivery as reference
I tried using WMMBXY but it didn;t work.
Pls let me know asap.Your help is appreciated.
Thanks and Regards
Priti
Edited by: Priti Adukia on Feb 11, 2008 4:48 AM

Hi Nicole,
What I've to do is quite the same as the case. Outbound and Inbound are in the same SAP system. If I've good understanding, I must set partner profile as follows :
INBOUND - Parter LI with
                        Message DESADV
                        Operation code DELS
OUTBOUND - Partner KU
                        Message DESADV
                        Operation code ???
Please advise
Suchart

Issue while trying to create Sales Order from Inbound Idoc ORDER05

Hi All,
I am trying to create a sales order through an Inbound idoc ORDERS05 created out of a Purchase order. The header pricing conditions from the Purchase orders gets populated in E1EDK05 segment and this needs to go to the Sales order header conditions while trying to create the Sales order.
But when the fields are getting incorrectly mapped to the Sales order. Issue being, the segment E1EDK05-BETRG contains the condition value. But this fields gets populated to the KOMV-KWERT (condition value) screen field on the Sales order header conditions. But this should have got mapped to field KOMV-KBETR (Rate). If I look at the Purchase order, E1EDK05-BETRG is the field getting fetched from field KOMV-KBETR on the Purchase order. So this should have correspondingly got mapped to KOMV-KBETR on the Sales order as well.
This looks like a standard behavior. But if any of you have encountered this issue before please let me know if any Correction instructions are available for the same. If this some issue in Pricing conditions configuration, do let me know.

Hi Paaavan
You can set a break-point include "FV45PFAP_VBAP_BEARBEITEN_VORBE" that is called by both the SAP Standard and BAPI where the data is prepared and checked in the internal table XVBAP. Compare both SAP standard VA01 and your 'Z' program for what may be different in XVBAP.
I think the problem my be with regards to the business_object number that is hardcoded in the standard function module. It has given me issues before and hence I tend to use the function module SD_SALESDOCUMENT_CREATE to create sales documents with.
Regards,
Marius

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.

Non English characters conversion issue in LSMW BAPI Inbound IDOCs

Hi Experts,
We have some fields in customer master LSMW data load program which can
contain non-English characters. We are facing issues in LSMW BAPI
method with non-English characters Conversion. LMSW steps read and
conversion are showing the non-English characters properly with out any
issue. While creating inbound IDOCs most of the non-English characters
replaced with '#' and its causing issues in creating customer master data in
system. In our scenario customer data with non-English characters in
the first name, last name and address details. Any specific setting
needs to be done from our side? Please suggest me to resolve this issue.
Thanks
Rajesh Yadla

If your language is a unicode tehn you need to change the options like IN SAP you need to change it to unicode in the initial screen Customize local layout(ALT F12) options 118 --> Encoding ....

Inbound idoc for orders05 to create sales order

Hi all,
I am creating a sales order through idoc (ORDERS05). I am getting a flat file, which is being converted into idoc from XI side and i need to add certain things and validate inside the function module IDOC_INPUT_OREDERS. I am using the exit call customer function '002' (EXIT_SAPLVEDA_002) in it.
My confusion is regarding the population of control records. If some validation fails, i need to set current status as 51. Which field i need to update in this exit in order to achieve this. What are the other control fields that i need to update for an inbound idoc please specify.
Also, i have another doubt, what is the use of DXBDCDATA in that exit. Do i need to do any BDC related work in inbound idocs.
I am new to inbound idoc scenario. But havn't found enough tutorial related to standard idoc generation..
thanks

Hi,
I think, you should fill the validation errors in EXIT_SAPLVEDA_011 (SD EDI Incoming Orders: Final Processing of Internal Error Tables) which subsequently update the status records of IDOC. Check line NO 56 of function module "IDOC_INPUT_ORDERS".
Regards
Vinod

Inbound IDoc w/message ORDERS - issues with error processing

We are using inbound IDoc ORDERS05 with message type ORDERS to create the sales orders in SAP. In WE20 we have the following settings:
- partner type LS (= Sales Org VKORG)
- process code ORDE
- trigger by background program
- post-processing agent of type US (user) with a user ID.
We create IDocs through an ABAP program and use RBDAPP01 to post the IDocs. When there is an application error in the IDoc posting we expect the designated user to receive a workflow item in the SAP Inbox, but for some reason this is not happening.
I did some research and went through all the possible settings for workflow, task, etc. and everything seems to be set up correctly. When debugging RBDAPP01 I have noticed that it calls FM APPLICATION_IDOC_POST_IMMEDIAT, which, in turn, calls IDOC_START_INBOUND. If IDOC_START_INBOUND returns SY-SUBRC = 1 then the workflow item is sent correctly to the designated user, exactly as we want. But for some reason it returns 0 (I changed it to 1 in the debugger).
It seems that IDOC_START_INBOUND reads TEDE2 records (TEVE2-EVCODE = ORDE) and sy-subrc = 1 is only possible when EDIVR2 is 1,2,3 or 4. In our case TEDE2-EDIVR2 = 6. It seems that TEDE2 is maintained in the transaction WE42. However, I tried to change the settings there but it affects the IDoc processing in whole (IDoc gets some odd status and doesn't get processed as before). I've also tried to use process code ORDE_BY_WORKFLOW in WE20 with the same "success".
What do we need to do to get a workflow item for the errors that happen in the application layer when IDoc is posted? Is it even possible with this message type?
Any ideas would be appreciated.

Hi,
Can you please share how do you overcome the problem, so that it can be helpful for others.

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (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.Both should be succesful
2) Create Port Using Transaction Code IDX1
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 XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (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.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(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)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (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
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Inbound IDOC error while processing Invoice

Hi All,
I received the following error while processing an Invoice on an inbound IDOC:
Field BSEG-MEINS - does not exist in the screen SAPMF05A 0300
Message no. 00349
Diagnosis
The specified field does not exist on the screen
Procedure
Check your batch input data
Any assistance will be greatly appreciated.
Thanks, Inno

Hi
Please check which G/L Accounts were involved and verify that the Field BSEG-MEINS was set to 'optional' in Transaction OB14. The correct Field Status Variant
for the Company Code can be viewed with Transaction OBY6 and the Field
Status Group for G/L Account can be found with Transaction FS00 under
the Create/bank/inter Tab. This should eliminate the Error 00 349.
Regards
Javier

Help required in posting inbound idocs

Hi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena George

Hi,
We are facing a problem during integration testing to post inbound idocs.
The scenario is :
A custom FM is written to process the inbound idocs, which does the following processes in sequence.
1. BAPI used to create Goods Receipt
2. BDC used to create Delivery using VL01N
3. BDC used to create Handling Unit using VL02N
4. BDC used to create Post Goods Issue using VL02N
The VL01N creates a deivery, and using that delivery BDC calls VL02N to create HU.
In unit testing the idocs are success, but when multiple idocs are used in integration testing, all fails either during delivery creation or HU creation.
The error message we often get when HU is failed is : "Runtime error RAISE_EXCEPTION has occured ".
We have also incorporated a commit work and wait of 5 seconds after each BDC to avoid locking problem if any.
The partner profile is set to ' trigger by background program'.
Standard program RBDAPP01 is scheduled to collect the IDocs in status 64 and then to be processed.
The package size used is 1, inorder to process idocs one by one to avoid locking.
Should any object type be given in RBDAPP01 ?
If so, is it required to maintain any record for that object type in table TBD55 to process idocs serially in RBDAPP01 ?
Any help in this regard is appreciated.
Thanks in advance
Regards
Meena George

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.

Inbound IDOC basic type HRMD_A07: Why no validation available?

I am using a standard inbound IDOC basic type HRMD_A07 to update employee master data (IT0000 & IT0001). However, i found out that this IDOC just directly updates to the infotypes without any validation. For example, i provide an invalid company code (BUKRS) and personnel area (WERKS), the IDOC still updates into database without any proper validation.
Filled the following fields in the IDOC segments:
E1PLOGI
plvar=01, otype=P, objid=00000001, opera=I
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0000, begda=20120101, endda=99991231
E1P0000
pernr=00000001, infty=0000, endda=99991231, begda=20120101, massn=01, massg=01, stat1=3, stat2=3
E1PITYP
plvar=01, otype=P, objid=00000001, infty=0001, begda=20120101, endda=99991231
E1P0001
pernr=00000001, infty=0001, endda=99991231, begda=20120101, bukrs=XXXX, werks=XXXX, persg=1, persk=EC, abkrs=99, plans=00000111, otype=S
Please help me out in case I am missing something. Thanks.

Additional Info:
In WE21 at the TRFC Port, it is possible to set this Option:
Send Only Fields of Selected Segment Version
The segment data of the IDoc is passed to this port with the length matching the segment definition of the release specified in the partner profile.
But if we are using an reduced message type, all fields of the newest release are in the segement.
The docu tells that this will be done in function EDI_DOCUMENT_OPEN_FOR_CREATE.
But it is never called when createing an material IDOC with BD10.
Bug or feature?
Kind regards
Manuel

Inbound Idoc set up..

Similar Messages

Maybe you are looking for