Error when posting the IDoc

Hi,
Now i am working on a File (XI) to IDoc (R/3) scenario. In XI, I went to the TCODE "idx5", there is no error. But When I went to the TCODE "idx5" in R/3 side, it showed me the follwing error...
"No authorization to send IDocs with message type ZEMPINFMSG".
What role should i assign to the user?

Hi Jeya,
Have you tried to post IDocs from the R/3system?...goto we19 and try to send an IDoc. In XI, to check if the IDoc has reached-t-code is IDX1..
Regards,
Sushumna

Similar Messages

Error when posting the goods receipt

Hi we have recently successfuly updated 4.6 B to ECC 6.0.But when i am doing captive consumption by 949 Mvt. through process message system gives an error that
Error when posting the goods receipt
Message no. CB345
Diagnosis
With the selected process message, a goods receipt for the order was reported to the warehouse (destination ZPI1). However, an error occurred when the goods receipt was posted.
Please do needful.
Regards,
PP

Hi Daniel,
This is the first time i am coming across an issue like this.
neverthless from a logical front,
1. Remove Cost center as a valid receiver in Settlement Profile.
2. Your OKB9 setting are pretty much good. No need to worry about it. Becasue, OKB9 only will work if the system doesn't identify any other cost object. In this case Production Order is an automatic cost object which system should have taken.
3. Check the Settlement rule when you have created Production Order. It should have been MAT.
4. I hope you are creating Production Order with Material (using CO01 and not CO07)
5. Make sure in OPL8, the default rule in controlling tab is PP1.
Once all these are fine, i do not see any reason why you will get your probelm.
Please check and revert back to me if the problem still persists.
Best Regards
Surya

Error while posting the Idoc 'Update error, transaction VA01'

Hi Gurus,
When an inbound Idoc for sales order is trying to post we are getting the error 'Update error, transaction VA01'.
Aslo following are the details of the error:
Update error, transaction VA01
Message no. 00377
Diagnosis
An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
during a synchronous update.
The error was caused by the transaction VA01.
Update information
Return code: 009
Text : Error during insert table FPLTC (RC= 1, Key= )
Procedure
Pleas analyse your Batch-Input data.
You can also examine your posting data using the transaction SM13.
Can somebody let me know what would be the cause.
Also the we are trying to post the Idoc with a Id which is having maximum Authorization.

Hi,
Where you able to resolve your issue, I would appreciate if you can share the solution.
Thanks

Error in posting the Idoc....

Hi Experts,
When I post the Idoc from the external system to the SAP,I am getting the
error as application document not posted and status code as 52.so what I need
to do to overcome this error,please help me over this issue.
Regards,
Kiran.

Hi,
you have to check the idoc in debugg mode and pull it out the reason why i has 52 and you know how to debug inbound - go to we19 and here give any existing idoc no and press F8 and enter into screen, in that select 'INBOUND FUNCTION MODULE' select give ur standard F.M name and select the background mode.
or thre way is goto BD87 make the correct the error idoc manually.
--Use Tcode BD87 to check for IDocs that are not been processed and reactivate.
u can find here if any data wrong or missing.
<b>Reward if useful</b>
Regards,
Vijay

Error while posting the 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.
Even in f-22 also it is not asking for the same.
In Idoc all the item level values are coming prorperly.
If anybody worked on such issues then please reply.
-Thanx.
-Umesh

Hi,
Where you able to resolve your issue, I would appreciate if you can share the solution.
Thanks

Error while posting the IDOC. Status message '56'

Hi,
I have a requirement where I will post an IDOC which inturn will split the original IDOC into child IDOCs based on the store value.
I am trying to post the IDOC in WE19. So, the Original IDOC is posted successfully with status '53'. Whereas, the child IDOCS finished with error. The status of the message is '56' and the error says 'EDI: Partner profile not available'. Could someone tell me what could be the reason for this..?
Actually, the IDOC was created by the Functional Consultant. So, should the partner profile creation also done by them or do we need to do anything to solve this problem.? Could someone answer me this question. Thanks in advance.
Best Regards,
Paddu.

It looks like the control data for the child segment is not getting populated. you have to find the code which populated the control data and see if it is doing what it should.

Error when posting debmas idoc

i have test run the debmas idoc, when iexecute it i got an an error ' NO BATCH INPUT FOR SAPMF02D 0340 SCREEN' is displayed.. please help me..i have used debmas06 as basic type

Hi,
usually this is due to a field which is either in display only, either suppressed in the online transaction XD01 or XD02.
Try to figure out which field is the one by looking at the data in the idoc in comparison to the fields ready for input in the online transaction.
Alternatively, you can try to process the idoc using the idoc test tool transaction WE19.
Process it using function module IDOC_INPUT_DEBITOR and process the customer master data transaction in order that it jumps online at the first error.
This should help to investigate.
For the fields settings transaction look into OVT0 and OB20
BR
Alain

Error when posting the Delivery

Hello Everybody,
When I am trying to PGI the delivery, I see the following error -
"Posting only possible in periods 2008/11 and 2008/10 in company code SCIL"
When I tried to close the posting period in MMPV, I see this error.
"Incorrect period in control rec. of CoCd SCIL; no conversion
The current period (month/year) of the control record is112008"
My company code Variant is M4.
Can someone tell me where am I going wrong.
Thanks,
Sneha.

Hi
Menu path to t code OB52
img-financial accounting new-financial accounting global settings (new)--ledgers-fiscal year and posting periods-posting periods-open and close posting periods(OB52)
First of all you must see what the posting period varient maintained for your company code SCIL
This you can see in OBY6 (in processing parameters tab you can see that) and what the fiscal year varient maintained in your company code SCIL in t code OBY6
In that take your fiscal year varient say K4
In that take your posting period varient say 1000
Then in OB52 you have to maintain like this
1000--S-blank---zzzzzzzzzz--01-2009-12-2009---13-201016---2010
1000--A-blank---zzzzzzzzzz--01-2009-12-2009---13-201016---2010
1000--+-blank---zzzzzzzzzz--01-2009-12-2009---13-201016---2010
1000--D-blank---zzzzzzzzzz--01-2009-12-2009---13-201016---2010
1000--K-blank---zzzzzzzzzz--01-2009-12-2009---13-201016---2010
1000--M-blank---zzzzzzzzzz--01-2009-12-2009---13-201016---2010
1000--V-blank---zzzzzzzzzz--01-2009-12-2009---13-201016---2010
If you maintain entries like this your error will be resolved
There are many more opinions available regarding OB52
Please make a search
If it is real time issue please take the opinion of your FI person
Regards
Raja

Error when posting a SOAP request

Hi all,
Facing error when posting the SOAP request and after entering the Server Username and password giving error that http not found and url
The URL i follow is http://<hostname>:<port>/XISOAPAdapter/MessageServlet?version=7.0&channel=:BusinessSystem:PI_SOAP_CC
can any one of you tell me in place of XISOAPAdapter what should i place?
Please help me to post the SOAP request to PI server.
Thanks in advance ,
Manohar.

Hi ,
copy the same URL (Endpoint that you had given while generating wsdl file) to the browser and chek the status. ( http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel)
See the below URL for the same i.e. SOAP adapter...http://help.sap.com/saphelp_nw04/helpdata/en/fc/5ad93f130f9215e10000000a155106/content.htm
You should get response something like this '
Message Servlet is in Status OK
Status information:
Servlet com.sap.aii.af.mp.soap.web.MessageServlet (Version $Id: //tc/aii/30_REL/src/_adapters/_soap/java/com/sap/aii/af/mp/soap/web/MessageServlet.java#15 $) bound to /MessageServlet
Classname ModuleProcessor: null
Lookupname for localModuleProcessorLookupName: localejbs/ModuleProcessorBean
Lookupname for remoteModuleProcessorLookupName: null
ModuleProcessorClass not instantiated
ModuleProcessorLocal is Instance of com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0
ModuleProcessorRemote not instantiated
This is make sure that webservice endpoint is given correctly. Don't forget to give username and password for connecting to XI server. user should xiappluser .
Ranjeet Singh.

Error while posting the CREMAS03 Idoc

Hi
I a getting the Error while posting CREMAS03 idoc from File
The ERROR: Status 65 ,Error in ALE Servics: Cross Company code does not exits..
but when i cheked with the functional guys , the comany code exits..
Any one have any idea
SV

Hey,
    seems you have given wrong enteries for logical system in sale or in WE20(patrner profile)
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.

Error when posting IDoc *** in system ERP100

Hi Experts!
Can you pls help me with a goods receipt issue?
When user tries to make a good receipt on a PO, we have the msg "Error when posting IDoc *** in system ERP100" in SRM front-end application monitor.
The same msg is getting displayed in RZ20.
On the idoc itself in tcode WE02 however, I can't see any problem and unfortunately I have no access to the same t-code in R/3. Anyway, I don't see the GR on the PO.
What can be the reason for this problem please?
What is in general the way to analyse and solve this kind of issue?
Thanks a lot !!
imre

Hi,
First find out the PO number from the idoc in tx WE02 in SRM system. Then in ERP , transaction BD87 , specify the details like message type and the system information .... and find out the PO that was errored out for GR. From this we can find the cause of the error. First try to rectify the error and then run the report to clear the contents of BBP_DOCUMENT_TAB.
Hope this helps.
Regards,
Kalyan

Error oocuring after posting the IDOC

Hi
i am getting a error in a scenario
the scenario is Idoc to file. when we post the IDoc, its getting posted successfully. but the pipiline is getting failed at the inbound message when monitoring in SXMB_MONI.
i am getting the following error
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIAdapter</SAP:Category><SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_NO_REQUEST</SAP:Code>
<SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/>
<SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/>
<SAP:Stack>ALEAUDIT IDoc cannot find request IDoc in Integration Server
</SAP:Stack><SAP:Retry>N</SAP:Retry></SAP:Error>
all the experts help me out in solving this issue

Hi Deepika,
their might be some problems with ur ALE settings.
Here is a detail of the steps to be followed.
Do verify whether u have done the steps or repeat the steps as stated:
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)

Error when activating the master data

Hi
I am getting the following error when activating the master data. when using IDOC as transfer method in transfer rules
<b>Error while creating table 'EDISEGMENT' entry '/BIC/CIRB0CLASS_NUM_TEXT'</b>
If anyone came across this kind of problem plz share the solution.
Regards
Annie

Hi
I solved the problem. AFter changing from PSA to IDOC, i just saved first and activated. it got activated. But thanks for the response.
There are no short dumps in ST22
Regards
Annie

Error when posting goods issue

hi gurus,
can anyone please help me with this error when posting goods issue to a free issue sales order " line item text is mandatory for vendor invoices".
thanks in advance

Dear Ysabella
It seems the item texts is not maintained in the order which is made as mandatory.
Go to sale order VA02, select that line item and click on "GotoItemTexts". There maintain the relevant text and retry.
thanks
G. Lakshmipathi

Getting the below error when running the Baseline.grf for the first time

I am getting the below error when running the Baseline.grf for the first time.
Appreciate your support in resolving it.
Error below:
INFO [main] - *** CloverETL framework/transformation graph, (c) 2002-2012 Javlin a.s, released under GNU Lesser General Public License ***
INFO [main] - Running with CloverETL library version 3.2.1 build#63 compiled 04/01/2012 12:53:21
INFO [main] - Running on 4 CPU(s), OS Windows 7, architecture amd64, Java version 1.6.0_20, max available memory for JVM 901120 KB
INFO [main] - Loading default properties from: defaultProperties
INFO [main] - Graph definition file: graph/Baseline.grf
INFO [main] - Graph revision: 1.114 Modified by: mkressirer Modified: Thu Apr 12 13:27:18 EDT 2012
INFO [main] - Checking graph configuration...
INFO [main] - Graph configuration is valid.
INFO [main] - Graph initialization (Baseline)
INFO [main] - [Clover] Initializing phase: 0
INFO [main] - [Clover] phase: 0 initialized successfully.
INFO [main] - register MBean with name:org.jetel.graph.runtime:type=CLOVERJMX_1306871483270_0
INFO [WatchDog] - Starting up all nodes in phase [0]
INFO [WatchDog] - Successfully started all nodes in phase!
INFO [RUN_GRAPH1_0] - Running graph ./graph/InitDataStore.grf in the same instance.
INFO [RUN_GRAPH1_0] - Checking graph configuration...
INFO [RUN_GRAPH1_0] - Graph configuration is valid.
INFO [RUN_GRAPH1_0] - Graph initialization (InitDataStore)
INFO [RUN_GRAPH1_0] - [Clover] Initializing phase: 0
WARN [RUN_GRAPH1_0] - WS messenger cleanup failed.
java.lang.NullPointerException
     at org.apache.axis2.client.Stub.cleanup(Stub.java:134)
     at com.opensys.cloveretl.component.WebServiceClient.free(Unknown Source)
     at org.jetel.graph.Phase.free(Phase.java:487)
     at org.jetel.graph.TransformationGraph.freeResources(TransformationGraph.java:681)
     at org.jetel.graph.TransformationGraph.free(TransformationGraph.java:955)
     at org.jetel.graph.runtime.PrimitiveAuthorityProxy.executeGraph(PrimitiveAuthorityProxy.java:149)
     at org.jetel.component.RunGraph.runGraphThisInstance(RunGraph.java:511)
     at org.jetel.component.RunGraph.runSingleGraph(RunGraph.java:409)
     at org.jetel.component.RunGraph.execute(RunGraph.java:302)
     at org.jetel.graph.Node.run(Node.java:414)
     at java.lang.Thread.run(Thread.java:619)
WARN [RUN_GRAPH1_0] - Some graphs wasn't executed (because graph "./graph/InitDataStore.grf" finished with error).
WARN [RUN_GRAPH1_0] - Some graph(s) finished with error.
ERROR [WatchDog] - Graph execution finished with error
ERROR [WatchDog] - Node RUN_GRAPH1 finished with status: ERROR caused by: Graph './graph/InitDataStore.grf' failed!
ERROR [WatchDog] - Node RUN_GRAPH1 error details:
org.jetel.exception.JetelException: Graph './graph/InitDataStore.grf' failed!
     at org.jetel.component.RunGraph.execute(RunGraph.java:324)
     at org.jetel.graph.Node.run(Node.java:414)
     at java.lang.Thread.run(Thread.java:619)
INFO [WatchDog] - [Clover] Post-execute phase finalization: 0
INFO [WatchDog] - [Clover] phase: 0 post-execute finalization successfully.
INFO [WatchDog] - Execution of phase [0] finished with error - elapsed time(sec): 2
ERROR [WatchDog] - !!! Phase finished with error - stopping graph run !!!
INFO [WatchDog] - -----------------------** Summary of Phases execution **---------------------
INFO [WatchDog] - Phase# Finished Status RunTime(sec) MemoryAllocation(KB)
INFO [WatchDog] - 0 ERROR 2 20132
INFO [WatchDog] - ------------------------------** End of Summary **---------------------------
WARN [exNode_0_1306871483270_RUN_GRAPH1] - Attempt to unregister non-registered thread in the ContextProvider.
./graph/InitDataStore.grf: Execution of graph failed! Error during graph initialization: Phase 0 can't be initilized.
INFO [WatchDog] - WatchDog thread finished - total execution time: 2 (sec)
INFO [main] - Freeing graph resources.
ERROR [main] - Execution of graph failed !

It can't find an Endeca specific class when running via the clover command line utility. Thus, the classpath being set in that shell script is not incorporating the .jar files where the endeca-specific classes are packaged. I would start by adding an line to see what your classpath is set to. There are actually already some lines of shell script in clover that you can uncomment to see what .jars are getting loaded:
#echo $CLOVER_LIB/*
for i in $CLOVER_LIB/*.jar $CLOVER_LIB/*.zip; do
     LOCAL_CLASSPATH="$LOCAL_CLASSPATH:$i"
done;
#for i in `ls $CLOVER_LIB/*.jar`; do
#echo $i
#done;
You could also echo LOCAL_CLASSPATH to see what is getting set there. At the end of the day, you will need the endeca-specific jars to load which can be found here: /Endeca/Discovery/2.3.0/Integrator/plugins/com.endeca.latitude_1.0.0/*
HTH,
Dan
http://branchbird.com

Error when posting the IDoc

Similar Messages

Maybe you are looking for