IDoc Assistance

Hi All,
I would greatly appreciate any assistance that you'll can provide, with an IDOC - XI - IDOC asynchronous scenario that i am working with.
The IDOC being used is ACC_EMPLOYEE_EXP02. I am sending info from an SAP HCM - XI - SAP ECC system.
However, currently when i test my scenario, i get the following error, on the receiving system: Function module not allowed: APPL_IDOC_INPUTI
I dont believe that the process code on the inbound partner profile is the issue as, i am using the same IDOC and process code in another scenario (file - xi - idoc), and this works fine.
Any ideas?
Regards,
Nilesh

Hi ,
Check all the settings needed for an R/3 - XI- R/3 scenario..... In ur case R/3 to XI is working fine and u have to check the XI-R/3 side.
Check the RFC destination ( Both in XI and in R/3)
Check the logical system name
PORT, Partner profile .....
Regards,
Jude

Similar Messages

For Assistance: IDocs in Status 02

Dear SAP Peeps,
We have some issues on an existing HR interface. Approximately 2 to 3 idocs per two weeks use to end after their generation in PGH. They end up in status 02-Error passing data to port. Error description is "codepage of receiver system can't determind. receiver destination was: BB1CLNT100".
I've checked the RFC destination, port settings, and connectivity and they seems to be ok.
Can you help me on how to solve this issue?
Thanks!

Worth to have a look at this thread
Error handling problem with outbound idoc status 02 and XML HTTP Port
Regards
Vivek
Reward points for all the useful answers

Customer/vendor could not be determined for IDOC

Hi all,
Am trying to post incoming payments through EDI ..
IDOC Information
IDOC type: PEXR2002
Message type: REMADV
Function Module: IDOC_INPUT_REMADV
Process code: REMA
Am getting these 2 errors :
Customer/vendor could not be determined for intermediate document
Company code could not be determined for intermediate document
Has anyone encountered this problem, if yes can anyone suggest the solutions, any help regarding this is highly appreciated.
Thanks.

Hi,
Currently I am facing with the same type error when trying to post incoming payments through EDI.
IDOC Information
IDOC type: PEXR2002
Message type: REMADV
Function Module: IDOC_INPUT_REMADV
Process code: REMA
I am getting the below error:
1. Company code could not be determined for intermediate document
I have maintained record records for partner type and partner number in OBCA.
Please advice what are the other configuration changes do I need to maintain.
Your assistance would be highly appreciated.
Thanks.
Edited by: Victor Collins on Feb 27, 2009 9:31 PM

Modify BP in CRM using Idoc type BUPA_INBOUND_MAIN_SAVE_M03

Hi,
I want to modify(add) a new role to an existing BP in CRM.
I am using the Idoc type BUPA_INBOUND_MAIN_SAVE_M03 for the same.
The problem that I am facing is that even though I am wanting to modify the BP, whenever this IDoc is posted the existing roles (seen in table BUT100) for the BP get deleted and the new role is added through the interface.
Please can anyone assist me as what is going missing in the filling the segments.
Regards,
Taher
the segment structure is as below.
BUPA_INBOUND_MAIN_SAVE_M03
E101BUS_EI_EXTERN
E101BUS_EI_HEADER
        E101BUS_EI_INSTANCE
    E101BUS_EI_CENTRAL_DATA
        E101BUS_EI_ROLES
            E101BUS_EI_BUPA_ROLES
                E101BUS_EI_ROLE_DATA
                E101BUS_EI_ROLE_DATA_X

Hi,
I figured out the solution to this.
Get the existing roles for the BP using the FM BAPI_BUPA_ROLES_GET.
Append the existing roles along with the new role that is required to be added.
the task type should be I (Insert).
When the Idoc is posted the existing roles do not get overwritten and the new role is added.
Regards,
taher

PROBLEM IN CUSTOM IDOC CREATION

Hi Friends,
                I'm facing a problem in custom idoc creation plz try to assist me
1.As per the information i have i'm creating segment in we31
for cremas01 idoc.But when i enter the name for segment i'm getting message "Name range Voilation particular name which i had given is not permitted in customer system?
Plz clarify this,and are there any formalities which i should look for before creating custom idoc?
Good answers will be rewarded.
                                                                          Regards,
                                                                           Vinod.

The Problem might be.... with the naming of the segment.
Standard segments should be created with 'E1' and all the custom segments are created using 'Z1' and the name with 8 characters long only is permitted.
Reward Points if useful.

IDoc Adapter Logical System Empty

Hello All,
For one of our scenarios for Reciver IDoc adapters we are getting the error "Receiver service cannot be converted into an ALE logical system ". On further investigation it seems the logical system stays on editing the Adapter Specific Message attributes option & even after clicking the Compare with SLD Option. Can you please assist us with this issue ? Also sldcheck runs fine but sldapicust gives an error CIM_ERR_FAILED. We recently upgraded our sld and we believe this might be the issue.
Thanks,
Kiran

Hi Debashish & Veera,
The issue has been resolved. When our SLD was migrated to a newer version 1 month ago back our logical system names got cleared. We did not face this issue until yesturday since the logical system names were still cached with the business system. Yesturday a newer IDoc scenario was imported in production and which caused the business system cache to be refeshed and it started pulling the new empty logical system name causing the scenarios to fail.
Thanks,
Kiran

Doubt on server proxy and file to idoc scenario

Hi,
     I could able to solve most of my doubts from this forum, many regards to all who assisted me.Here are some simple doubts plz help me in solving them.
          1.In FILE to PROXY scenario is it necessary to create rfc destination on IS and receiver system? becoz in some blogs it is written to create RFC dest only in case of CLIENT PROXY,since we XI adapter to connect receiver syst in case of server proxy?
          2.In FILE to IDOC scen at receiver side is it necessary to formalities in SM59,WE21,WE20 or just configure in WE20 to maintain partner profile?
          3. In case of single SLD for DEV,CON,PROD while transferring from DEV TO CON using file system how do we move file in EXPORT DIRECTORY TO IMPORT DIRECTORY of cons system?
          4.for transporting IR objects we can use TRANSPORT LIST or CHANGE LIST which will be more preferable?
          Plz kindly answer to any of questions u know ?
          Points will be rewarded for valuable answers.
                                                                                Regards,
                                                                                Smitha.

> 1.In FILE to PROXY scenario is it necessary
> to create rfc destination on IS and receiver system?
> becoz in some blogs it is written to create RFC dest
> only in case of CLIENT PROXY,since we XI adapter to
> connect receiver syst in case of server proxy?
You need to maintain the setting on your R3 system to connect to XI for the Transaction SPROXY as shown in the blog "How to Activate ABAP Proxies".
Apart from that as you are doing a file to proxy via XI, XI would need to send data to the R3 system . For this, you can either key in the Details of the R3 system in the XI adapter directly or you can maintain a HTTP destination on your XI in SM59 and use this in the XI adaper.
> 2.In FILE to IDOC scen at receiver side is
> it necessary to formalities in SM59,WE21,WE20 or
> just configure in WE20 to maintain partner profile?
Just the partner porfile. SM 59 and We 21 are used for port and RFC destination and as it is XI that is posting the Idoc these steps are not needed on R3
> 3. In case of single SLD for DEV,CON,PROD
> while transferring from DEV TO CON using file system
> how do we move file in EXPORT DIRECTORY TO IMPORT
> DIRECTORY of cons system?
You have to go to the Folder Level / OS level of your XI server, copy the files from the Export DIrectory and move these manually to the import folder of the CONS server. This is for both IR and ID objects.
> 4.for transporting IR objects we can use
> TRANSPORT LIST or CHANGE LIST which will be more
> preferable?
If you perfrom File Transport, the imported objects will be available under the Import Change List and you need to activate this Import Change List.
Regards
Bhavesh

BW system not receiving Idocs from R/3 system

Hi all, I am having a problem with my BW system. What happened is that we deleted logical systems in R/3 and then recreated them but now in BW we can't display received data. We checked using rsa3 extractor checker and the data is available in R/3 but we are failing to bring it across to BW. BW is saying there is no data. And the monitor status when loading data is reporting missing messages that is: Request received, Number of sent records and Selection completed. May you assist me it's urgent because all BW work has stopped because of this.
Thanks in advance!!

Hi, we recreated RFC destinations but the problem still remains. This is the message under my Monitor status on the "Details" tab:
Overall status: Missing messages or warnings.
Requests(messages): Everything Ok.
   Data request arranged
   Confirmed with: OK
Extraction(messages): Missing messages
   Missing message: Request received
   Missing message: Number of records sent
   Missing message: Selection completed
Transfer (Idocs and TRFC): Missing messages or warnings
   Request Idoc: Application Document posted
   Info Idoc 1: sent, not received; Data passed to port OK
   Info Idoc 2: sent, not received; Data passed to port OK
   Info Idoc 3: sent, not received; Data passed to port OK
Processing(data packet): no data
I think the messages above may assist in a big way for you guys who are willing to assist. I am a bit stuck on the issue.
Thanks once again in advance!!

Purchase order already exists error for change Idoc 860

Hi all
I am getting an error that purchase order number already exists, when i try to post change inbound IDoc 860. How can I fix this issue?
Thanks in advance

This can be b'coz of Check purch.order no is active (A - Check whether the purchase order number already exists) in your sales doc type (TCode VOV8) used for the transaction.
So, if for your business process, one PO number can be mention in more than one sales orders. Then maintain Check purch.order no should mention as <Blank> - No Check under your sales doc type used for transaction's General Control. Or else use diff. PO Number.
Hope this can assist you.
Thanks & Regards
JP

URGENT! Idoc Message Type FIDCC2 Not Posting CO Documents

Hi Everyone,
Our company is just about to begin using message type FIDCC2 to post entries through FB60/FB65 and FB50. When you manually enter an entry through any of these transactions, an FI, CCA and PCA document are all created simultaneously. However, when posting an identical entry through message type FIDCC2, only an FI document is created. Why are the other documents not being created and is there something that I am missing from configuration or some sort of trigger that is supposed to create the other entries? Please assist as this is extremely urgent.
Thanks to all that can assist,
Pete

Hi Peter,
Is your company uses any of the profitability segment fields as well? If so how are you updating this information on to the FIDCC2 idoc and how are you generating any COPA document simultaneously. I am in the same situation and my FIDCC2 idoc updates the FI, CO, PCA components but not the COPA. I am not sure where to populae the Profitability segments on the FIDCC2 type. Please share if you have same issues in your company.
Regards
Elphick

Payext Idocs Issue

Hi,
I am generating payext idocs off the back of a payment run (F110). The issue that I have is where I am paying a supplier with multiple invoices, that the individual invoices are all included in the IDOC. When the bank statement is returned to us, for this type of example, the bank statement is delivering all of the invoice references in the Payment Notes section. I am being informed that this is due to my system sending out segments E1EDP02 009 / 010. I am also informed that I need to make changes in FBZP - "Payment methods in Company Code". So far my settings (under payment advice control) here are:-
1. Note to payee lines on form - None
2. Payment Advice output according to number of lines - always payment advice
Also in the DME I am using program RFFOEDI1 and have amended the variant in the output control section to only generate 2 "number of " invoice details.
Is anyone able to advise please.

Hi,
This thread has been created some time ago and recieved no response. Can you please close if you feel this issue/query has been resolved in the meantime. If it has not then please provide additional information in relation to your query. By providing updates to your thread it moves you thread to the first page of thread and increases visibility and possiblity for the multiptude of experts in SDN Forums to offer their support.
Therefore please update with more information or close thread.
Thank you for your assistance.
Regards,
Brendan.
(ERP FI/CO SDN/WIKI Moderator)
http://wiki.sdn.sap.com/wiki/display/ERPFI/ERP+Financials

Problems in IDOC receiver communication channel

Hi,
I am trying to build an interface to get data from 3rd party legacy system using JDBC and post the data into ECC using IDOCS. I have IDOC built in ECC, I am able to import the metadata in IDX2 after creating port in IDX1. But after building the whole interface, I dont see the IDOC receiver communication channel which has to post IDOCS in the ECC 6.0 system.
Please assist.
Rgds
Kishore

OK in that case, we are getting the following error in the Message monitoring:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code>
<SAP:P1>-BS_AVN_TO_FILE_JDBCSERVER</SAP:P1>
<SAP:P2>-BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:AdditionalText>
<SAP:Stack>Problem occurred in receiver agreement for sender -BS_AVN_TO_FILE_JDBCSERVER to receiver -BS_WOAV_IDOC_SENDER,urn:sap-com:document:sap:idoc:messages.ZAVENTITY01.ZENTITY: No standard agreement found for , BS_AVN_TO_FILE_JDBCSERVER, , BS_WOAV_IDOC_SENDER, urn:sap-com:document:sap:idoc:messages, ZAVENTITY01.ZENTITY</SAP:Stack
Please check and assist.
Rgds
Kishore

IDoc extension not passing to PI at runtime

Hello Gurus,
We have a DELVRY05 IDoc which was extended with a new segment. This has been working very well and is in our production environment. We are now in develpment with a new modification and have added two new fields to the extended segment. We are able to import the IDoc and complete the mapping changes in PI using the new fields. However, when we test the changes, we do not see the new fields being populated in the Inbound Message Payload.
I have searched through many of the existing forums which led me to perform cache updates. Still we have the issue.
We are using ECC and PI 7.0.
The new fields are visible in WE02.
The new fields do not show in the Inbound Message Payload in PI.
We have updated the following:
Java VM Cache Refresh:SLD Cache
Java VM Cache Refresh:Value Mapping Guid Cache
Java VM Cache Refresh:Value Mapping Group Cache
Java VM Cache Refresh:Value Mapping Value Cache
Java VM Cache Refresh:Cache for Softwarecomponents
Java VM Cache Refresh:Adapter metadata
Our Basis guy then did these:
Xi Data Cache Refresh: http://<system>/CPACache/refresh?mode=partial
Xi Data Cache Refresh: http://<system>/CPACache/refresh?mode=full
Any assistance that can be provided will be greatly appreciated.
Thomas

Hi,
Have you tried IDX2??
Mark the idoc type for which you have added extension and delete it.
The first time you send the idoc through it will be added to IDX2 again and have the new fields.

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

Storage of IDOC definitions in Integration Repository

Hi there,
I'm trying to define development standards for the use of XI and I can't seem to find any recommendation for the storage of SAP interface definitions (IDOCs, RFCs, etc)within the Integration Directory.
We have an environment with multiple SAP systems including regional R/3 systems which have differing definitions of standard IDOCs - eg different ORDERS05 IDOCs, so do I need to store these definitions in system specfic SWCV?
My thought is to create a Product in the SLD (OUR_BASIS) with multiple SWCV relevant to specific SAP systems (OUR_BASIS_R3_EUROPE, OUR_BASIS_R3_USA etc) each of which could be brought into the Integration Repository to store the system specific objects. The names are non-SID specific to prevent naming issues moving through development, quality and live XI environments. I would then link the product to each of the SAP systems in the SLD, adding new SWCV as more systems are put into the SLD.
Does this seem like a reasonible solution? Does anyone else have or know of other recommendations?
I will be grateful for any assistance and will dish out reward points as appropriate.
Many thanks,
- Ian

Hi Ian,
I tried to understand the reason of why would you want to create custom software components in your SLD for multiple SAP systems and import IDocs arising out of these systems into different software component versions? I guess this would defeat the basic purpose of developing objects under software components and the idea of developing integration objects (mapping, data type etc) under software components and not based on phycial system or geographical location.
Let's take an example. If you consider software component X release 1.1 installed on SAP system A. Consider this is a standard software component version delivered by the vendor. And you don't have any authorization to change the objects under this software component. In such scenario, whether you have this software component installed on SAP System A or B or C you just need to import it once under that software component version. Say IDoc ORDERS05. Irrespective of which system you download it from, it's definition is going to remain the same.
Also, system dependencies and actual source and target definitions should not be part of your software component versions. They should be in Integration Directory and should be kept independent of the software components.
Any custom development will be obviously grouped under custom software components.
Message was edited by: Anand Shankar
Message was edited by: Anand Shankar

IDoc Assistance

Similar Messages

Maybe you are looking for