INBOUND IDOC issue

Hi,
I'm facing the following problem:
A program reads a file from a directory in the unix server itself and populates an IDoc. No BDC is involved.The file contains all the data required to populate the IDoc like control record, data records etc. But when the IDoc is posted, it fails giving the message " Receiver port in the control record is invalid ". But when I try to reprocess the IDoc through WE19 without changing anything, I'm able to process it successfully by giving the Inbound Function Module corresponding to the process code.This is not happening in the case of Standard Inbound. I'm using a file port with ALE services but not EDI.All the other configurations are maintained.
Please suggest a solution.
Thanks,
Raj.

Hi Rajgopal,
for an inbound idoc no need for port configuration.Please see whether u have done all the configurations correctly.Also if this is inbound that means u r updating to SAP , so already data will be available in control record and data record.So please check the sender information and the receiver information.check the port the sender using.
For a custom function module,custom message type,custom basictype,the below configurations r generally done.
1>we81
2>we31
3>we30
4>bd51
5>we57
6>we42
7>we20
In we20 u have give u r zmessagetype in the inbound parameters and also u r custom process code.
Regards,
Nagaraj

Similar Messages

DESADV01 inbound idoc issue- Mappping to LIPS-LICHN

I have an Inbound Idoc DESADV01 , I want the e1edp09-charg field to be moved to LIPS-LICHN field of the New Inbound delivery.
How can this be done.
Regards,
Sugopa Ray

Hello Sugopa
When you look through the coding of IDOC_INPUT_DESADV1 you will find user-exit fm's of group XTRK.
However, instead of EXIT_SAPLV55K_004 I assume that EXIT_SAPLV55K_001 is the one you should pay your attention. This fm has the following interface (on ERP 6.0):
FUNCTION EXIT_SAPLV55K_001.
*"*"Local Interface:
*" IMPORTING
*" VALUE(IDOC_CONTROL) LIKE EDIDC STRUCTURE EDIDC
*" VALUE(IDOC_SEGMENT) LIKE EDIDD STRUCTURE EDIDD
*" EXPORTING
*" VALUE(PROCESSING_PROTOCOL) TYPE DELIF_T_PROTT
*" CHANGING
*" REFERENCE(DELIVERY_HEAD) LIKE VBKOK STRUCTURE VBKOK
*" REFERENCE(DELIVERY_ITEM) TYPE DELIF_T_VBPOK " <<< contains field LICHN
*" REFERENCE(PACKING_HEAD) TYPE DELIF_T_VERKO
*" REFERENCE(PACKING_ITEM) TYPE DELIF_T_VERPO
*" REFERENCE(ISC_ENHANCEMENT) TYPE ISC_EXIT_SAPLV55K_001 OPTIONAL
INCLUDE ZXTRKU03 .
ENDFUNCTION.
Regards
Uwe

Inbound idoc error in R/3while distributing GOA to R/3

Hi,
We have faced below inbound idoc issue for service GOA while replicating GOA to R/3.
When distributing contracts for external services the system issues message SE120 (Number range conflict (internal package no. & already assigned)). How can this be prevented?
Please advice us,
Many Thanks,
Venkat

Hi
You can change Type from Service to MATERIAL and release again.
W
It will go successfully.

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

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

Issue in inbound Idoc

Hi Experts,
I have one issue inbound idoc, actually we have 4 zfields, durring inbound process this 4 fields getting the records as well as its showing the correct values in we05. Even the idoc also getting success. But in the sales order its not showing the values. I debugged the program, its getting the value and showing the value in idoc.
Can anyone help that why its not showing the records in particualr screen in sales order?
The four fields are date related fields.
Anyone suggest me what we need todo?
Mohana

*Populate work area with custom date fields
        lwa_vbak_date-zzdate3 = lwa_zgvsa_e1edk03-zzreqshipdt.
        lwa_vbak_date-zzdate4 = lwa_zgvsa_e1edk03-zzshipnltdt.
         lwa_vbak_date-ZZCAN_DATE = lwa_zgvsa_e1edk03-zzcindbydt.
        lwa_vbak_date-zzdate6 = lwa_zgvsa_e1edk03-zzddelaftdt.
*Move work area to DXVBAK
        MOVE-CORRESPONDING lwa_vbak_date TO dxvbak.
Its taking the value and showing the value in IDoc, but not showing in the screen.
Pls guide us.
Mohana

Issues during Contract creation using Inbound IDOC BLAORD03

Dear Experts,
We need to create Contract using Inbound IDOC BLAORD03.
I am facing following issues and need some one's help ASAP.
(1) Contract is generated without Header Texts and Item Texts through IDOC BLAORD03 .
(2) Not able to create CONTRACT for service masters using Inbound IDOC BLAORD03.
Is there any body who has implemented this scenario and able to guide ?
Looking forward to help ASAP.
Thanks in Advance,
Best Regards,
Mitesh Desai
[email protected]

Hi All,
I am also facing the same issue. I am trying to upload service outline agreements thru LSMW using idoc basiv type BLAORD03 ( FM->IDOC_INPUT_BLAORD).
Immediate help highly appreciated.
Thanks & Regards,
Vijender

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

Problem with user exit EXIT_SAPLIEDI_001 for Inbound Idocs in replacing G/L

Hello all,
I am currently facing an issue where my IDOC where exit EXIT_SAPLIEDI_001 is not appearing to work properly.
Basically I am using the FM that processes the inbound idoc (IDOC_INPUT_INVOIC_FI) to post an accounting document. We needed a solution where we need to substitute one of the G/L Accounts.
The current process in our SAP system is that we are creating a billing document which automatically generates the output type (running: program rsnasted subroutine edi_processing) to create and process the inbound idoc.
So I discovered FM EXIT_SAPLIEDI_001 which exports company code and G/L Account back does this.
In this exit, Since I needed to get data from the IDOC, I used the logic ASSIGN: ('(SAPLIEDI)IDOC_DATA[]') TO <fs_edidd> to get the DATA Records for further processing.
During the development and testing phase in the Sandbox system this works.
However when we moved this to production we encountered a situation where the G/L account was not being substituted so were assuming EXIT_SAPLIEDI_001 is not working properly. However when I reprocess this in production either by running the idoc with errors RBDMANI2 or BD87 the IDOC is properly posted and the G/L Account is substituted as well as if I try to repeat the output type of the billing document. So there are instances when in the actual business scenario it does not work except when I reprocess it.
I was wondering if there are any ideas why this could have happened?
Oh ... I also noticed when we transported the objects of the exit. When I try to double click the subroutine I made inside the exit it said the object does not exist. I had to generate the function group of FM EXIT_SAPLIEDI_001 in SE80 in production for it to reflect. I was wondering if this could have caused the issue.
Well I hope to hear from you.
Regards
Edited by: Rob Burbank on Dec 6, 2011 1:03 PM

Hi,
Check in t.code CMOD whether project is active or not (Activate the Project)
BR,
Vijay

Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan

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.

Error while processing inbound Idoc (HRMDA_07) with FM IDOC_INPUT_HRMD

Hello,
I have a inbound Idoc of type HRMD_A (basistype HRMD_A07) which is processed by Function module (FM) IDOC_INPUT_HRMD with proofing. After processing an Idoc the status Monitor for ALE messages (BD87) tell me that my Idoc has status 53, which should be the result i would like to have.
Unfortunately when i go to transaction PA20 and check the infotypes, i see that infotype 0302 isn't created. When analyzing this problem i see that during the processing the Infotypes are posted with HR_MAINTAIN_MASTERDATA (dialog mode is 0 and luw_mode = 0 from include LRHA2F02 FORM save_pa_pb_infty) When this is done for infotype 0302 sy-subrc <> 0 the message is A complex application error has occured. This error message is placed in Export parameters
Return and Return1
of HR_MAINTAIN_MASTERDATA. When the program returns to the calling Form it checks if there is message of type E in HR_RETURN (see below) :
CALL FUNCTION 'HR_MAINTAIN_MASTERDATA'
 EXPORTING
 pernr = ins_objects-objid "#EC DOM_EQUAL
 actio = 'INS'
 tclas = tclas
 dialog_mode = dial_mode
 luw_mode = '0'
 no_existence_check = $cross
 no_enqueue = $cross
 IMPORTING
 return1 = return
 hr_return = hr_return
 TABLES
 proposed_values = proposed_values.
 REFRESH proposed_values.
 IF hr_return-msgty = 'E'. "note 984409
 CLEAR protocol_error.
 protocol_error-msgty = hr_return-msgty.
 protocol_error-msgid = hr_return-msgid.
 protocol_error-msgno = hr_return-msgno.
 protocol_error-msgv1 = hr_return-msgv1.
 protocol_error-msgv2 = hr_return-msgv2.
 protocol_error-msgv3 = hr_return-msgv3.
 protocol_error-msgv4 = hr_return-msgv4.
 READ TABLE t_hrobjinfty WITH KEY objid = hr_return-pernr
 infty = hr_return-infty
 subty = hr_return-subty.
 protocol_error-segnum = t_hrobjinfty-segnum.
 protocol_error-routid = 'create_prf_pa_pb_object'
As mentioned above, the error message is only placed in the parameters Return and Return1 and not in HR_RETURN.please read the first reply

Hi,
I think you have preety much done from your end itself .
Could you please tell me what you got in this parameters:
 protocol_error-msgty = hr_return-msgty.
 protocol_error-msgid = hr_return-msgid.
 protocol_error-msgno = hr_return-msgno.
 protocol_error-msgv1 = hr_return-msgv1.
 protocol_error-msgv2 = hr_return-msgv2.
 protocol_error-msgv3 = hr_return-msgv3.
 protocol_error-msgv4 = hr_return-msgv4.
It may help us to track down the issue in more better way .
Thanks!

Processing Inbound IDOC's from FTP.

Hi,
I have an issue where IDOC's (WPUBON01 & DEBMAS01) are being saved in ftp folder and once these IDOC's are saved, we have to process it in SAP System, i would like to know the simple way of having these IDOC's processed in Unix based SAP system as the IDOC's will be coming in at Real time evey minutes or Seconds.
is there a way to do it with out ABAP process i mean just by using the Unix Scripts or by triggering the SAP background job.
Thanks in Advance.

Hi,
for testing purposes you can trigger inbound IDoc processing in transaction WE16. Otherwise you can schedule program RSEINB00 to periodically import IDoc into system. You can make a copy of that program and made changes if you need to add some extra logic.
Cheers

INBOUND IDOC issue

Similar Messages

Maybe you are looking for