Error on released

hi friends,
I can release my order because i recieved this error: Order type PI01 plant ABC: No checking rule maintained for operation..how can i maintain this checking rule?
thank you so much...

Checking rule is maintained in OPJK.
These checking rules are defined in path SPRO > Production > SFC > Operations > Availability check > Define Checking rule) for the order types
Here u define combination of plant and order type
Note that in order to carry out a material availability check you need a checking group and a checking rule.
Checking group is maintained in MRP3 and u can find it in OVZ2
Against this checking group u need to define scope of check in OPJJ
Do all these settings and check
Rgds
Edited by: Vicky Khabrani on Jan 25, 2008 10:43 AM

Similar Messages

Error while releasing a request.

Hi All,
I'm facing an error while releasing a request.
The request contains an ABAP programs along with two INCLUDDE programs as well as a TCode to run the same.
It is running successfully in dev. server. But, while releasing ths request it shows me the following error :
" Object REPT ZBAPI_SD_SERV_SALES_ORDER is inactive " ,
where ZBAPI_SD_SERV_SALES_ORDER is the program name. When I checked out in ABAP editor it shows the program active.
But, I'm unable to understand why its showing me an inactivation error.
Guys, help me out in this.

Hi,
Check if the INCLUDE program are also ACTIVE. They must be in inactive state. Try activating them and release the request.
Regards,
Vikranth

Vf02 error while releasing a billing doc to accounting

Hello All,
I m getting the below mentioned error while releasing a billing doc for a accouting.
I have checked all the settings in vkoa , ob52 and many more and all are set properly, now m not able to track where actually the prob is.
error is: No account is specified in item 0000001004
Message no. F5670
Diagnosis
No account was specified for account type "S" in item "0000001004" of the FI/CO document.
System Response
The Financial Accounting program cannot process the document.
Procedure
A system error has probably occurred in the application you called up. Check the data transferred to item "0000001004" of the FI/CO document.
Points wil be rewarded
Thanks,
SUnny

Hi,
Have you checked what is the determination account determination log ? You can do this by entering in VF02 and select from the menu Environment -> Account Determination Analisys -> Revenue Accounts.
In this log you can see what are posting keys determined from the pricing procedure that should be posted in the FI document and determine very easy in which step the account was not determined.
After that you can maintain the correct account in VKOA transaction.
BR,
Valentin

Error while releasing Billing doc to Accounting

Hi all
I am gettin the following error while releasing a Billing doc to FI-
Reconciliation account 240001 or short key 00 is not permitted
The Billing doc pertains to Export sales and the billing Doc type is Export Invoice. However the Customer Recon A/c is defined as 240000 which is for Domestic Sales. A/c 240001 stands for Export Sales. I am wondering why it is asking for the Export Sales Recon a/c. Does this has something to do with Alternative Recon A/c? Should I set an Alternative Recon A/c and check this? If yes, then should it be defined in SD or FI?
If any1 has come across this prob, plzz help me.
Regards

It is all Fi related, and should be defined by the Fi Consultant.
But by changing the sort key I think your error can be solved. But I don't exactly know your config settings to recommend any solution.
Regards
AK
Please reward if helpful

Error in releasing transport in XI using CTS+

I am getting the following error while releasing a transport in XI 7.0 system. Here is the error log
Full Message Text
Error occurred during hmi call: CMS -> XI; method = writeChangelistData
Thrown:
MESSAGE ID: com.sap.aii.ib.core.transport.api.rb_TransportCsException.UNSUPPORTED_RELEASE_PREFIX
com.sap.aii.ib.core.transport.api.TransportCsException: Unknown import source prefix XI7_1_XI_CONTENT.tpt99badd10521711dfa213001b78df49b6.tmp
at com.sap.aii.ib.server.transport.impl.utils.FileUtils.getSerializationReleaseId(FileUtils.java:499)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:715)
at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importXiStream(InternalTransportServiceImpl.java:500)
at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importXiStream(TransportServiceImpl.java:265)
at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:306)
at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl1_0.process(HmisLocalLocalObjectImpl1_0.java:144)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:291)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:212)
at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:507)
at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:655)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)
Serialized server exceptions:
Any help would be appriciable. We already have a message open with SAP and checked various notes and threads to correct the issue but no luck
Thanks,
Pankaj

Hello Bjorn,
How did you get this solved?
I'm having nearly the same issue:
A custom-table with a total key lenght of about 365 characters. As soon as I enter a special character (_) in the key field just before the position 120, the message tk287 rejects the entry. Entering the special character in a key field at about key position
60, there's no message rejecting the entry.
Regards

Error while releasing credit block for the order

Hi all,
I am getting follwing error while releasing credit block for the order in VKM1
Incorrect index structure for table IVBEP1
Text
Incorrect index structure for table IVBEP1
Diagnosis
Internal error.
Procedure
Repeat the transaction.
If the error occurs and you have a CRM System connected to your SAP R/3 System, the document may have been archived in the CRM System.
If the error occurs again, inform your system administrator. If the error cannot be corrected, call the SAP Hotline directly. Describe which steps preceeded the error.
But we are not transfering any orders to CRM.The order can be only seen in R/3
Please assist
Regards
Mano

Hi
KIndly check the oss note 505876 in may help you
Regards
Damu

Error while releasing an activity from NWDS

Hi,
I am facing the below error while releasing an activity from NWDS - transport view.
Internal error: the export of SC_CR com.xxx.xxx/xxx_SOFTWARE_COMPONENT#Track_D.118 failed. tcs returncode was 12
Check in and activate was successfull and in CMS, the activity is shown as activated.
Please help me to rectify this error.
Thanks in advance!
Regards,
Manchari. N

Make sure you are connected to NWDI server.
Also create a new activity for a different component in the same track.
Below links may be helpful :
http://wiki.sdn.sap.com/wiki/display/TechTSG/(NWDI)(CMS)PropagationRequestReleaseinTransportViewFails
NWDI/CBS - release activity in consolidation
Re: Error on Release of activity (Version set not found!)
Regards
Deepak

Error while releasing the custom table

Hi Everyone,
Modified the User defined include files of a particular table for one of our requirements ( In the function group of the table maintenance generator ) and encountered an error while releasing the request to Quality server, the error disappeared after regenerating the table, this seem to be happening only when the user includes of a table maintenance is introduced/modified, why the release doesnt work when there is any change in the maintenance generator?,
Rgds,

Hi Sailatha,
After modifying, you need to re-generate everything so that, the changes come in effect.
Trying to release without re-generating will surely result in error.
Regards,
Raj

Error when releasing a transport

Hello experts,
I am getting an error when releasing a transport. The error message is telling me that
Object DTPA DTP_009C8T81IIB6H4UFC7FQUVRFL was set to 'inactive'
The detailed error message isnt very helpful. The performance assistant gives the error message RSO 407.
I found another thread, scn.sap.com/thread/3428031
The answer in this thread appears to be very close to a solution for me, I just need a little more information I think. As it says, I have looked in the table RSTRAN for the transformation that this DTP processes. There are three rows, with a different OBJVERS. A and M are both set to ACT, but OBJVERS = D is set to OBJSTAT = INA.
I suspect that this is the problem with the releasing of my transport. Do you agree?
If so, how do I go about getting this activated?
Many thanks.

Hi Simon,
The D version will be always inactive as it indicate SAP Delivered version of the transformation.
I will suggest just have a look at any existing transformation, you will find same status i.e D version INA also check last change it will be SAP also under content column you will find info for D version.
I still say, just go ahead and release your transport by ignoring the message, it should work. You are all set to move your transport.
Rest upto you.
I have tried releasing transport by ignoring messages many times.....and worked all time
Thank-You.
Regards,
VB

Error While Releasing the Billing Document Msg No. KE/AD 243

I am getting error while releasing the billing document
Error No KE/AD 243
This error comes in particular billing document only others are posted correctly.
Rgds
Dhiraj

Dear Anil
We had applied EHP3 enhancement, before EHP3 is working fine with no transfer sign assignment but after EHP 3 it gives the error and not in all billing document but in particular document only. so i think there is no changes required in KE4I.
Rgds
Dhiraj

Error While Releasing Accounting Document & Proforma Invoice--URGENT

Dear Gurus,
I am facing problem in below cases.
-- Proforma Invoice canot be cancelled ....If i need to cancel then wht needs to do
-- I created New Material Master again old material and made sale getting Acc determinatin error while releasing accouting document.. But in old cases( old material) no problem like this. Y like this.
Pls guide me.
Regards,
Venkat

Dear All,
Thanx your kind replies. I analysis and foud following:
Access       Message                    Description
05       123                    Access ZKOF not carried out
Access     Complete
Field Condition Table          Value in Doc
Chart of Accts          CAIN
Sale Org                          1000
Plant                           F201
AccAssg Grp          01
Acct Assgn. Grp          05
Account Key          !! ( Showing Yellow Indicator)
Above things showing Against Condition TYpe JEXT.
I checked in Pricing procedure and condition Type JEXT....against this no Accounting key assigned.
No problem faced earlier...now showing like this........y.
Regards,
Venkat

Error while releasing Billing: Assign HD00 (Frieght) Condition type in COPA

Hi,
I am getting the below error while releasing billing document.
Assign condition HD00 type in COPA
HD00 condition type is frieght condition type
Is it good thing if we assign this condition type to COPA value field in KE4I? or we should not assign Frieght condition to COPA?
Please advise
Thanks
Kishore

HI Kishore,
To which GL account are you posting this freight condition value? Is that GL created as a revenue element (of category '11'/'12')?
If yes (has to be 'yes', since you are getting the error message), then you don't have a choice but assigning a CO-PA value field in KE4I. The idea here is, if you have created the GL as revenue element, then you intend to take it to Controlling module for further analysis. Thus, making your FI/CO reconciliation easy.
If you do want to carry this value to CO-PA for analytical reporting then don't create that particular GL (assuming you are posting freight to a separate GL) as a revenue element. That said, it does make sense to carry this value to CO-PA and in your present case, you don't have a choice as the message which you got is an error message, which you can't circumvent.
Hope this helps.

Error while releasing Billing Document in VF02

Hi,
I am getting the below error while releasing the billing document in VF02. What could be the reason for this?
Characteristic value US does not exist for characteristic WWCST (Country Ship-to)
Message no. KE0C133
Diagnosis
The characteristic "WWCST" ("Country Ship-to") should be posted to Profitability Analysis (CO-PA). When the system checked the entries, it was established that the transferred characteristic value (" US") is not valid in CO-PA.
System Response
The data is not consistent and therefore cannot be transferred to CO-PA.
Procedure
With the function Maintain Characteristic Values, you can add characteristic values to those that are valid.
Thanks
Babu San

Hey,
Nicolas' reply is correct.
And in case you could not maintain the relevant table and want to undo the
check against the check table for some chars you have to remove the check
table from table TKEF and afterwards regenerate the check routine RK2FGPKE.
I will explain this more in detail on the basis of an example: imagine you want
to get rid of the check table for char WW123. You must then proceed as follows:
1.) Remove the entries for fields CHTAB and CHFIE from the TKEF record
    for WW123 (that means FIENM = WW123) so that these fields are after-
    wards initial in table TKEF for the WW123 record.
2.) Execute function module RKD_SHORT_TEXT_GENERATE for APPLCLASS = KE
    so that program RK2FGPKE is regenerated.
But please be careful about this workaround and test it throughly in your DEV or QAS
system before apply in PRD system.
Best Regards
Young

Error in releasing billing to accounting

Dear Friends,
I am facing an error while releasing the billing document to accounting.....error is "only output tax is allowed for acount 175000 9999, 01 is not allowed"......what wud b the reason?.....thanks in advance....

Hi
Go to FS00 and give you company code and G/L account 175000 and check in the control tab wheather the Tax tab is properly maintained or not
Secondly , check for tax condition record you maintained ( say MWST) in VK12 and in VK12 check what tax code you have assigned , If you have assigned tax code 01 then check wheather it is a input tax or output tax .If it is a input tax then change it to output tax by assigning a output tax code
Finally also check in SPRO->Financial accounting->Basic settings->Procedures wheather the tax code is properly maintained or not .I think 01 is a taxcode which is input tax code just check in the
Regards
Srinath

Error while releasing an invoice for accounting.

Hi Experts,
I am encountering an error while releasing an invoice for accounting. The error displayed is 'error in transaction currency'. Please help me out with this.
Regards,
Sunita

Hi Rish,
Simply go to FS00 and click on edit cost element and for CElm Category give some input based on the G/L account type.
You might have to seek help of an FI consultant to do so.
Also in KA01 create this G/L account as a cost element against your controlling area assigned to your Chart of Accounts, you can do so by clicking on Extra's tab in transaction KA01.
Just let me know if it works.
Reward if helpful.
Regards
Ravi

Error while releasing PO : System error: block object EKKO, Key PO Number.

Dear All,
I am getting error while releasing PO : System error: block object EKKO, Key PO Number.
Please help to resolve.

Hi Friend,
How the issue is resolved, because i am facing the same issue, while positing Service entry sheet.
If you can give us solution, it will be more useful and more appreciated
REgards
RS

Error on released

Similar Messages

Maybe you are looking for