Error in sending IDOC for PO

Hi,
I am facing a problem in PO for sending IDOC. The error message is "Error transferring Extension data for enhancement CI_EKKODB"
Message type is PORDCR1
Idoc type: PORDCR101
Diagonosis given:
THE UNDERLYING CUSTOMER ENHANCEMENT CONTAINS DATA REFERENCES THAT ARE NOT CHARACTER-LIKE. FOR THIS REASON THE SYSTEM WILL NOT TRANSFER DATA.
Could anybody please give any suggestion to resolve rhis.
Waiting for quick response.
Best Regards
Bapi

It seems you must change all elements in structure CI_EKKODB as charter type.

Similar Messages

Sub: How to send idoc for IW31.

Dear All,
Content: My requirement is to send the idoc for maintanance order- IW31. I found the message type as IORDER. I am not able to use change pointer IORDER is not matching, as i am not able to find the message type, when executing BD21 (for change pointer).
Please let me know the procedure for sending idoc for IW31.

This is what it worked for me, to create an INBOUND IDOC to transaction IW31:
I converted BAPI_ALM_ORDER_MAINTAIN to an IDOC
1) In transaction SWO1 copy model BUS2007A to ZBUS2007A (make sure set the status to implemented Edit->Change Release Status->Object type -> to implemented.
2)In transaction BDBG, check Object type, Object ZBUS2007A, Method ORDERMAINTAIN
you can check
http://help.sap.com/saphelp_nw04/helpdata/en/78/21740f51ce11d189570000e829fbbd/content.htm
I Put in Message type ZORDERMAIN
IDoc Type ZORDERMAIN01
the function name will be: ZIDOC_INPUT_ZORDERMAIN
3) configure transaction BD51
4) Configure transaction WE57
5) Configure transaction WE42
6) and Finally Transaction WE20
In my case it worked, still I modified function ZIDOC_INPUT_ZORDERMAIN, and in the call function to BAPI_ALM_ORDER_MAINTAIN I commented the releationship tables.(They were giving me some errors)
Hope this info will help someone.
Regards

Send Idoc For Purchse Order

Hi Friends,
I have Configure All the things require to send idoc for purchse order..........when i m creating purchase order from source system
it's getting send to traget system....................
but in target system giving error in idoc.that
VKORG, VTWEG, SPART cannot be determined for customer S004 , vendor 0006000023
i m using message type....ORDERS............
can antbody pls tell me how to maintain VKORG, VTWEG, SPART
in oreders message type.......there no fields in this message type.......i have checked it through se19...............

Hi ,
I have same problem ,
How to send IDOC of Purchase Order to URL of our vendor.
The Idoc is created , but how to send it to the web?
Anyone knows?
Thanks
Edited by: Moshe Stein on Feb 28, 2008 11:08 AM

Error in Sending IDoc to XI

Hi Gurus,
We are not being able to send Idocs from one of our Back-end SAP system. The Idoc status in we05 is successful but it doesn't reach XI. So we checked in SM58 in the Back-end R/3 system and there it shows the error:
No Service For System SAP*** , Client *** in Integration Directory
We tried almost every possible setup
-The System is defined in SLD and has the logical system name.
-The Adapter Specific Identifiers are correct for the corresponding business system in ID
-The RFC destination in R/3 system is defined.
- Read through other similar threads in SDN about the similar problem.
Do anyone have a more definite solution for this particular problem? The other R/3 systems are connected to XI system and all IDocs from those systems are arriving at XI.
Waiting for your valuable advices!
Regards,
Suddha

Hi All,
We had eventually found the solution to this problem we were facing in sending IDoc, though I couldn't manage to update the thread with the solution. I think this would be a very helpful information for those who face similar problems.
Let me describe the scenario first briefly,
We are sending an IDoc (Idoc extension), from SAP system to XI and then send the XML payload as mail attachment to the receiver via receiver mail adapter. Since this is a cross company transaction, hence we have configured the scenario as a B2B in ID, which means we use Parties for both the sender and receiver.
Now in the ID we had done all necessary configurations and used parties and services under Party. For the sender SAP system we assigned a Business System to Sender Partner, configured the Party Alternative Identifiers correctly. The ports were created in IDX1.
On the other hand the SAP system was also configured successfully - including Partner Profile, Distribution List, RFC destinations and ports.
In SLD we created Business System for the SAP system and in ID the Business System under party had the correct logical system name as Adapter Specific Identifiers.
But after all these, the IDoc was not arriving at XI, though in R/3 the status of the IDoc was 03 in we02. When we checked in sm58 in R/3, it showed us the error message that "No Service For System SAP*** , Client *** in Integration Directory".
The cause to this problem was:
We created (assigned from SLD) Business System only under Party (Sender), as this was a B2B scenario, and didn't create (assign) a Business System without Party, as we didn't need one at all in the scenario configuration. And this the reason behind this error. When an Idoc arrives at XI, before the Inbound IDoc adapter converts the IDoc to IDoc XML using IDoc metadata............it checks in Configuarion to see if any Service without Party (Busniess System) is defined for the Sender SAP System and Client (The SNDPOR and MANDT field values from IDoc Control header are taken as the SAP SID and Client). If it finds one it accepts the IDoc and starts the Normalization (Sender Party, Service......in the message header) and IDoc to XML conversion. If it cannot find an Service without Party in ID for sender system, it rejects the Idoc with the error message that we saw in sm58 in backend R/3 system.
In this step the Service under Party doesn't help, because at this point the Inbound IDoc adapter can not deterimine the sender party.
Hence for sending an IDoc from an SAP system to XI, we need to have an Service Without Party in ID, whether or not we require it in our actual Scenario Configuration, which is ofcourse not a case for the Reverse Scenario, ie Sending an IDoc into SAP system from XI.
This is the similar with BC adapter as well. I was already aware about this behaviour of BC adapter from my past experience and this actually helped to troubleshoot this IDoc adapter problem.
This was ofcourse a useful and new learning for me and hope would be helpful to others as well. Let me know if anyone has any doubts on this.
Regards,
Suddha
Edited by: Suddhasatta Guha on Aug 28, 2008 1:03 PM

Error in sending Idoc :: Urgent

HI
we are trying to send Idoc DELINS and ORDERS to SUS system. when sending the idoc the following error occurs in SUS
StandaredMessageFault
An error occured within XI interface: An exception with the type CX_GDT_CONVERSION occured but was neithered handled locally nor declared in a RAISING clause Program: SAPLBBP_BD_MAPPING_SAPXML1; Include : ; Line
How ever the same works fine in Dev and QAS servers
Regards,
Anand

Hi
Please provide SRM-SUS and XI Version details.
Please go through the SAP OSS Notes, which will help ->
Note 782755 - Control indicator is not transferred from MM to SUS
Related Notes
Note 1062864 - Control indicator is not transferred from MM to SUS
Note 313925 - Example exit for EDI outbound processing (e.g. purchase order
Other OSS Notes ->
Note 885825 XML inbound: Dump in QuoteItemReferenceVersionID
Note 825169 XML: Bid currency in bid invitation
Note 819953 SRM 4.0 of SAP XML output of partner address data
Note 723680 Corrections in the mapping of SAP XML messages
Note 723594 - SRM 4.0 XML confirmation mapping error
Do let me know.
Regards
- Atul

SM58 - Error while sending IDOC

Hi,
I got the following error while sending the IDoc to a XI system.
"No service for system (Idoc adapter port), client 800 in Integration Directory"
Please let me know whether this is due to an error in network or application error.
Note: remote logon is not successful in the XI system
Thanks in advance
Edited by: RPN on Jul 1, 2008 11:46 AM

Hi RPN,
Plz do check the following things :
1. Verify the logical business system in SLD.
To verify --- Go to SLD home page ---> Technical Landscape --> Select Web AS ABAP --> Select the technical system --> Clients ---> Click on the client you used as Business system --> Here look for the logical system is defined or not.
2. Open ID---> Click on Objects --> Service Without party/Party > Double click on business system>On the tright side--> Service --> Adapter specific Identifiers ---> Check IDoc Adpater, Logical System.
3. Refresh the full CPA Cache (userid must be XIDIRUSER/PIDIRUSER)
http://<hostname>:50000/CPACache/refresh?mode=full
Regards,
Vinod.

Company code does not exist error while sending idoc

Hi Expert
I am trying to send idoc from one client(800) to another client(810).I have faced error Company code does not exist, searched scn ,Got solution if company code does not exist in reciever system(810 client) ,it will show this error .Then i have tried to give specific company code which is exist in 810 client also .But same issue is coming . So what exactly the issue can any one say .
More Info:FI(Finance) header items and line items are sending .
Thanks & Regards

Hi,
Your company code not activated for material management. Few pre-requisites to create material and one is to activate company code for material management
Please activate in T.code: OMSY,
[For example: For Fiscal year variant K4]
In OMSY steps, u have to enteru2026u2026u2026..
Company Code (enter your company code name 2001)u2026u2026u2026u2026u2026.
Company Name..
Fiscal Year of Current Period 2009
Current period (posting period) 03( )
Fiscal year of previous period 2008( will come automatic)
Month of previous period 02( will come automatic)
Fiscal year of last period of previous year 2008
Last month of previous year 12
Allow Posting to Previous Period (Back posting)
Disallow back posting after a change of period
Now create material with T.code; MM01
Regards,
Biju K

Error in Sending IDOC

Hi,
i am working with the Scenario IDOC to IDOC using middleware PI.
Done with Whole Process .
But when i Sending an IDOC through WE19 it went Succesfully(i checked it in WE05).
But when i checked in SM58. then there is an error in sending my IDOC.
Transaction IDX1: Port SAPETS, client 800, RFC destination contain error.
Please let me know where might me the problem ??
Thanks
Deepthi

Hi,
Check the RFC destination connection from PI to ECC... looks like there is connection from PI to ECC to retrieve the metadata....
HTH
Rajesh

Sending idocs for custom field

Hi
I need to send idocs when i save the data in field , the idocs should be send automatically when the data saved to field, please provide the solution.
Thanks
Moderator message: "spec dumping", please work yourself first on your requirement.
Edited by: Thomas Zloch on Jun 23, 2011 9:17 AM

Hi
In case you have created a structure for your custom fields and added it to the standard table then you would be looking for a user exit so that the data entered in those fields from the MM01 or MM02 screen gets stored into the database.
Over there you can trigger a custom event and start your approval workflow.
If the approval is given then set a parameter say Approval as X in the workflow.
Read the workflow container in your exit for this container element and if its value is X,then move the corresponding data to the desired structure or else clear it.
Lets say you have added fields in CJ01 and it has two exits for storing the data in database.PROJ is the table and custom fields added in CI_PROJ
EXIT_SAPLCJWB_002
move-corresponding sap_proj_imp to proj.
EXIT_SAPLCJWB_003 :
call F.M. swe_event create
wait for say a particular time limit after which it should be considered as auto rejected read workflow container for this approval value
if X
move-corresponding proj to cnci_proj_exp.
else.
fire another event to cancel the workflow.
endif.
I am not sure this would be an appropriate way but could be tried.

Error by sending IDOC-acknowledgements

Hello,
we have the following scenario:
R/3 IDOC -> XI -> Mail-Adapter
We want to receive acknowledgements from the adapter.
But we get the error "Sender XI Party http://sap.com/xi/XI / XIParty / xyz couldn't be transformed to an IDoc Partner".
Does anyone know how to solve this problem?
Regards,
Thorsten

Hi,
Ok then,
Only the IDOC-acknowledgements couldn't be sent back to the R/3.
1.By any chance, did you check the
IDXNOALE table: and see if the port, the
client of the sender, and the message type id there.If yes then that table lists and block your acknowledgement.
2. Check this, "Use transaction SXMB_ADM ( Integration
Engine - Configuration) to obtain system
error acknowledgments from pipeline
services of the Integration Server and
maintain the specific configuration
parameter ACK_SYSTEM_FAILURE of the
RUNTIME category.Whenever a system error occurs within the Integration Server, a system error
acknowledgment is sent back to the sender.But this is for system error acknowledgements.
3. Did you refer the guide: "How To Handle Acknowledgments for IDoc"
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
OR
https://websmp106.sap-ag.de/nw-howtoguides
Then go to exchange Infrastructure.
Regards,
Anirban.

Error while posting Idoc for customer invoice.

hi,
I m posting Customer Invoice through LSMW using IDocs.
Basic type is FIDCCP02 and message is FIDCC2.
While posting the Idoc I m getting error as:
'Document or line item does not exist for invoice reference'.
I m not getting the error why it is asking for invoice reference because
in FB01 it is not asking for any reference or anything.
In Idoc all the item level values are coming prorperly.
If anybody worked on such issues then please reply.
-Thanx.
-Umesh

Hi Umesh,
Try posting customer invoice through TCode - F-22. There it may be asking for reference number. Generally we post customer invoice by F-22 not from FB01.
If you are getting error you can add reference field in your LSMW it may be mandatory in F-22.
Ashven

Error While Sending Data for Currency Translation

Hello Experts,
I am trying to send data via template. Data is getting saved but I am getting following error displayed.
1.) When I try to enter data for a particular month then, error as FX-200.
2.) When I try to enter data accross months of more than year then , FX-045 and FX-310 error.
I had look on various SAP Notes available for the errors.
As per them, I ran Full optimization, I checked rates are maintained for previous year too, I checked for LC Currency Type Property is maintained as L.
But nothing Worked.
Currently only the 3 members are maintained in Rate Dimension, so exceeding the size limit cannot be an issue.
Kindly Suggest, what could be another possible reason for the errors.
Regards,
Apoorva Garg

Hello,
1.) I am getting issues for example for 2010.Mar, 2010.Dec, 2013.Dec, 2012.Dec
2.) Business Rules Maintained
3.) Business Rule called via Default Script Logic
// Default base level logic - applies to all base members in all dimensions
*INCLUDE system_constants.lgl
//Process_Each_Member = TIME
*RUN_STORED_PROCEDURE=SPRUNCONVERSION('%APP%','KPI_Working_Act_FX','','GLOBAL','%SCOPETABLE%','%LOGTABLE%')
*COMMIT
//*RUN_STORED_PROCEDURE=SPRUNCONVERSION('%APP%','KPI_Working_AOP_FX','','GLOBAL','%SCOPETABLE%','%LOGTABLE%')
//*COMMIT
Regards,
Apoorva

Error during sending IDoc from XI to R/3

Hi,
I get following error (transaction: sxmb_moni), when I try to send a IDoc from XI to R/3.
Error: Transaction IDX1: Port SAPI14_921, client , RFC destination contain errors.
When I go to transaction sm 59 and start this rfc-destination so it works fine.
Can anybody help me please?
Thanks.
Regards
Stefan

Hi,
I dont now how you pushed the IDOC form R/3 to XI..
Follow this particular way ....
Go to WE19 and execute the IDOC which you want to send and clicl the tab startoutboundprocessing....
then it hits the XI after couple of minutes and then
Go to the XI in that IDX5 where you can see the IDOC messages....
Amaresh

Problem to send idoc for a Good Receipt created

Hello all,
I have a problem when a good receipt has been created in EBP system the idoc has been generated with a message type MBGMCR.Why a idoc has not been generated with a message type WMMBXY in our system ?
I verify in a transaction WE20 and we have a correct message WMMBXY between a system EBQ and system back end.
Please help me for this problem.

Ok Mady,
then just reward this good response
PS: for IDOC exchange, this is the only message type changed by switching < 4.5B to >= 4.5B.
New message types can be added for contract distribution (BLAORD, COND_A, BLAREL).
Rgds
Christophe

Error during sending sales idoc

hi all,
i m getting error during sending idoc for sales.................
Error:Check value field assignment for Condition PN10.....
How to solve this...?
Regards,
Imran

friends.......argent.......

Error in sending IDOC for PO

Similar Messages

Maybe you are looking for