DBIF_RSQL_SQL_ERROR while creating planned order in ECC

Hi ,
Recently we have done the ECC6.0 migration. Migration in the sense
Server A ECC6.0 Maxdb to Server B ECC6.0 Sqlserver.
we took the database export from server A and imported to Server B.
After completing the migration we are facing a problem.
Using Trx code MD11 I am creating Planned order. It is giving Planned order XXXXX will be created.But when I go MD13 and try to retrive the same planned order it says the order XXXXX doesn't exists.
when I try to go back from MD13 it shows Express document "update was terminated" received from Author ************.
I am seeing a dump in ST22.
Error 22.04.2010 DBIF_RSQL_SQL_ERROR CX_SY_OPEN_SQL_DB
Cann't insert NULL into column "ADCODE" Table "RESB"
Column doesn't allow NULLS . Insert Fails.
Any Help is Appreciated.
Regards,
Guru.

Hi Srini,
Please kindly review and evaluate note 686357 for possible solution.
686357 able pool nametab length incorrect after Unicode
The following pools may be affected: ATAB, GLSP, GLTP, DVPOOLTEXT, KAPOL
Please kindly run report RATPONTC to reset the dictionary and nametab length in the note.
Regards,
Mauro

Similar Messages

Error while creating planned order in product view

I am getting following error when I try to create planned order for a product in a Location manually in product view using /SAPAPO/RRP5.
Error occurred while creating order
Message no. /SAPAPO/RRP251
I checked the product and resource. Everything looks good.
Block is available in the resource WMP1_2041_001 for characteristics specified in planned order.
Product master and PDS look good.
In the planning log, I see the following error message.
Plan explosion failed for product LBRA1050-661 in location 2041
Message no. /SAPAPO/RRP718
I have not found SAP notes for above error.
Can you pl let me know what this is due to?
Thanks,
Srini

Srini,
The message was created as a result of several notes, such as 1582997. There are others.
The implication is that you have an invalid source somewhere in your BOM. Maybe a bad component part, maybe a bad transportation lane, maybe an invalid BOM, or maybe a bad PPM/PDS.
If you can't find the problem using logical troubleshooting steps, have one of your programmers debug. Have him put breakpoints in FM /SAPAPO/RRP_PLORD_CREATE . If you are particularly lucky, you will find a developer that understands German, because all the internal comments in this FM are in German.
Best regards,
DB49

Error while creating Planned order in SAP PP

Hi ,
I am creating planned order for finished material and system has given below error - Please specify the order deadlines in ascending order.
SAP Message Error- Message no. 61009 Please specify the order deadlines in ascending order
Very first planned order get saved and we declare the production and business completed
Now creating second planned order , while saving system giving above error.
I am Taking Planned Order Profile LA -Stock order
Any solution ...?
Thanks in advance !!!
Deepak.

Hello Deepak,
Please adjust the order dates in the scheduling of the planned order. In normal production scenario operation completed end of the night shift and order finish date is possibly moved one day in the future for this reason we need to set the operation timing in 24:00:00 format
In your issue change date like this
End date : 30.06.2014
Start : 31.05.2014
Opening date : 31.05.2104
Check with this date, it’s work for you
Regards
Umesh Mali

Issue in Exploding Alternate BOM while creating Planned Order to PR

Hiii All,,
I have maintained a two BOM's for a finished material one for In House production and one for Sub contracting the components for the Two BOM's are different.
i have maintained Two Versions for the finished material also.
when i covnvert a planned Order to an Sub Contracting Purchase Requisition alternate BOM doesnt explode. i have also maintained a production version in the Purchase info record. Still the main BOM explodes.
i have to manually change the planned order and give the other production version ie not the Inhouse BOM.
After creating the PR then again i have to go planned order and change to the normal InHouse BOM.
Please Provide me the solution.
Thanx & Regards,
Kumar Rayudu

Hi
In order to explode your alt BOM in your PR do the following.
1. Maintian alt BOM
2.Maintain a Version using this alt BOM only. Do not select any routing /rcp group.
3.Give this Version name in your Inforecord (ME11).
4.Set the "MRP" field as "Record Relevant to MRP " in your Source List for the material.
5.In the material master, select the procurement type (MRP2) as " X " ( ie, both proc types).
I am sure it will work for you
Regards
Krishna

Error while creating sales order in ECC 6.0

Hi All,
I am creating sales order through VA01.
Error comes As "Repairs processing with cost management only for the main item"
The material which i am using is finished goods.

Dear Akilesh,
Just check whether the material - in MM - material type whether the Qty and value update has been ticked.
What order type you are using and what is the item category you are using?
Kindly let me know that also
Regards,
Sudhir

Run time error while creating sales order in VA01

Dear all,
In our develpment server(ecc 6.0),while creating sales order in VA01 for a sales area, when ever entering material number and quantity and press enter, it is giving error and taking to Runtime error long text showing syntax error in program RK2LSFOC
application patch level for both production and development is same.
can any one suggest the solution please
Moderator message - Cross post locked
Edited by: Rob Burbank on Jan 7, 2010 10:03 AM

ths

Runtime error while creating sales order in VA01

Dear all,
In our develpment server(ecc 6.0),while creating sales order in VA01 for a sales area, when ever entering material number and quantity and press enter, it is giving error and taking to Runtime error long text showing syntax error in program RK2LSFOC
application patch level for both production and development is same.
can any one suggest the solution please

Please note the error details
Runtime Errors         SYNTAX_ERROR
Date and Time          07.01.2010 17:43:06
Short text
Syntax error in program "RK2LSFOC ".
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPLKEAK" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
The following syntax error occurred in program "RK2LSFOC " in include "RK2LSFOC
" in
line 128:
"No component exists with the name "KWBRUM". ."
The include has been created and last changed by:
Created by: "SAP "
Last changed by: "SAP* "
Error in the ABAP Application Program
The current ABAP program "SAPLKEAK" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Please eliminate the error by performing a syntax check
(or an extended program check) on the program "RK2LSFOC ".
You can also perform the syntax check from the ABAP Editor.
If the problem persists, proceed as follows:
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
The following syntax error was found in the program RK2LSFOC :
"No component exists with the name "KWBRUM". ."
|    " "

Where/ how do I set SNP to create Planned orders with multiple line items?

Hi
Currently our SNP is generating planned orders on a daily basis, it creates a single order with a single line item per location.
Where/ how do set SNP to create planned orders on a daily basis to generate a single order with multiple line items per location, so therefore one planned order with multiple line items for a single location.
Thanx
Keegan

Hi Keegan,
In SNP (APO) it is not possible to create order with multiple line items.
But you can do some settings so that while planning system can do aggregation and disaggregation.
But your requirment should be set on Aggregation/Dis-aggregation logic.
Please follow the follwing links:
http://help.sap.com/saphelp_scm2007/helpdata/en/2c/c557e9e330cc46b8e440fb3999ca51/content.htm
Aggregation:
http://help.sap.com/saphelp_scm2007/helpdata/en/42/f731d078e73ee4e10000000a1553f6/content.htm
Disaggregation:
http://help.sap.com/saphelp_scm2007/helpdata/en/a6/ebefaf32e22e468355da304cc59387/content.htm
Please be sure that the setting of this logic will be at planning area level.
You can't change aggregation/disaggregation logic further.
Regards,
Santosh

I want to know about ATP check requirement .generally we assigned yes or no while creating sales order

I want to know about ATP check requirement .generally we assigned yes or no while creating sales order what it means when we give Yes or No. how pegging flows
Regards
virender

Virender,
Can you be a bit more specific about ".....generally we assigned yes or no while creating sales order....." Exactly what field(s) did you 'assign'? Screenshots would be helpful.
With respect to pegging; in general, ATP has very little to do with pegging. Pegging is more of a planning concept, and not an 'availability checking' concept. There are a few exceptions in APO, but they are not commonly implemented.
Can you elaborate about exactly what you want to know with respect to 'pegging' and ATP?
Best Regards,
DB49

Wrong production version picked for planned order in ecc after CIF

Dear experts,
I am new to apo and was working on Cif of transactional data to ecc after planning run in Apo.
we have active integration model and all the master data cifed in apo.
we are cifing ppds ppm which is converted into snp ppm.
The scenario is:
We have a product FG100 at Loc1. For this product we have five alternate PPM's in APO.
When we do SNP planning run, for some planned order it picked alternate 4 or 5 as source of supply. Which is alright.
The problem is when we see the same planned order in ECC it shows source of supply as alternate 1. i.e. planned order in apo with alternate 4 and planned order in ecc with alternate 1.
Is this the expected behaviour, or there is some configuration setting for this. We want that it shows the same source of supply in ecc as in SNP planned order.
Best regards,
AKS

Hi Vikas/Nandkumar,
thanks for the response, in my case the issue is that I have got two production versions in ECC. One production version is used for planning in CTM while the other version should not be considered in APO CTM for planning.
The productionj version which I am not using for planning, I can manually attach the version in ECC to the planned order and the planned order should get CIFed to APO with the source of supply and resource details.
Vikas after executing the report also the source of supply is not getting displayed in the planned order.
Is their a solution by which i can achieve the above results.
Thanks,
Sanjog

Stopping Planned orders to ECC

Hi All,
I am facing an issue in which the planned orders created in the simulation version are getting transferred to ECC. As per our scenario we dont want to move any Planned orders to ECC. Please advise me the way how can i stop the transfer of orders to ECC.
Regards,
Manjit

Hi Kenneth,
Thanks for your reply,
I had already stopped it Transfer of SNP orders to OLTP system. I have selected No Transfer in SNP Tab. But i have not tried selecting No SNP Planned Orders as i thought No Transfer itself means No order should be transfered. Is there any other way to stop orders from the active version.
Regards,
Manjit

How to restrict the order reason in Tcode Va01 while creating sales order

Hi Gurus,
My requirement is
while creating sales order in VA01
if order type is Zvol
than the list of order reasons has to be restricted.
Now 15 are coming from OVAU tcode
I need only 5 from these.
Thanks & Reagrds
kals.

Hi,
By doing the user exit in IW32 we achieved the requirement of restriction of maintenance order TECO functionality if any Service Entry sheet pending with reference of maintneance order.
regards
JKM

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

MRP Run can not create Planned order to Sales order

Hi,
I have a problem with planning run to sales order. We have a configurable material which have make to order strategy. MRP Run does not create planned order to some of our sales order. I think it has relation with schedule lines but i can not understand the problem.
If schedule line has 1 as confirmed quantity MRP run can not plan but 0 as confirmed quantity MRP Run creates planned order. How can i solve this problem?
Regards,
techmastere

Hi,
Order for which qty is confirming, check which schedule line is determined and which requirement type system is determining.
then in VOV6 for schedule line tick mark availability check & Transfer of requirement
for requirement class OVZG tick mark availability check & Transfer of requirement
Note: if schedule line is not relevent for availability check & ToR then system always defaul confirm quantity.
kapil

Error while creating sales order

while creating sales order for a particular plant there is error coming
NO NUMBER RANGE FOR DOC TYPE ZOS1VXBAK-AUARTSILD
PLANTXVBAK-VKBUR.
Intailly I have check the no series we have internal no series for all plant,the
number series which start 195000001, only one plant the giving the above error, rest all plant it is as applicable above series.
kindly guide me for the same.

Hi Sanjay
This is regarding number ranges defining and assigning tips which you can follow as below:
Whenever there is a new Sales Org being created, you will be required to maintain Number Ranges for Sales Documents which are allowed for your New Sales Area.
Number Ranges can be maintained Internally by the system, however it can be maintained externally also if you customize it accordingly.
In Standard SAP the Transaction code for Maintaiing Number ranges externally is VN01.
Defining - The same can be reached through in IMG as : Sales & Distribution>Sales>Sales Document Header-->Define Number Ranges for Sales Documents.
Here you provide the system a specific Number range as follows:
Number range Key Start Number range End Number Range+Current Number
For Example: If you want to propose the following Number Range
*1 9000076000 9000076999 0
The Current Number field will be kept zero as you are proposing new number range and no sales documents have been created on it , Obviously..
*1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that it should not be there in the system as existing.
If you propose a key that is there in the system or if the Number Range (Start and End Series) is there in the system already, the system will throw a message that Interval already already exists. So choose a key that is unique, and which is not there in the system.
Here , by making this , you are assigning a Key to a Number Range Series.
All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in any order. For example: !1, ^A, BB,Z*,M2.........
Assigning - In Assigning, you assign the particular Sales Document to the Number Range you have already proposed as above.
The Assigning Part is done as follows:
The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document type in V0V8.
This can also be reached in IMG by:
Sales & Distribution>Sales>Sales Document Header-->Define Sales Document Types
Locate the particular Sales Doc Type, and double click on it to display it configuration. Here you put the Two Digit Number key in the Field- "Number range External Assignment"
Besides this:
If a new Shipping Point is created then Delivery Number ranges are required to be maintained.
Similarly,
If a new Plant is created then Billing Number Ranges are required to be maintained.
Regards
Naren

DBIF_RSQL_SQL_ERROR while creating planned order in ECC

Similar Messages

Maybe you are looking for