/SAPAPO/SDORDER_DEL not removing ATP orders

Hi All
I am doing product deletion where I am getting message that ATP order exist for the same. I have checked table /SAPAPO/ORDADM_I & found that entries are present in this table. To remove these entries I use report /SAPAPO/SDORDER_DEL but it is not able to delete the orders.
Could any one pls let me know how can I proceed.
Hitesh.

Hi Hitesh,
I had a similar problem this week.
I could not find those ATP orders in the report /SAPAPO/OM_DELETE_INCON_ORDERS
Then i deleted the entries directly from the Table /SAPAPO/ORDADM_I and it worked.
Let me know if you find some other way out.
Regards,
Asheesh

Similar Messages

OBIEE Remove Default Order By

Hi,
My users have a specific request in a OBIEE report. The report is based on 2 tables connected directly to the transaction system in AS400/DB2. The reason is the report must show real-time data. So far so good, OBIEE is able to connect and show the live data without caching the results (disabled the cache for these tables).
The problem is they need to see the rows in a report in a chronological order (the newest row inserted on DB2 in the bottom). I don't have any cronological column in the table to apply the OBIEE sort. OBIEE Admin Tools shows the desired order when I click on "view data" option in the Physical Table. The records are being displayed exactly as I need.
When I created the report on OBI Presentation, I can see on Advanced Tab that it includes a default "Order By" clause in the SQL Statement. I was able to remove the distinct by disabling the database feature DISTINCT_SUPPORTED in the rpd file.
Also, I tried to comment the //SORT_TYPE = "binary"; in the NQSConfig.ini but it didn't solve the problem. Tried to use a logical ROWNUM column but AS400/DB2 does not support this type of column.
How can I get rid of the "order by" clause in a OBIEE report? I must have to disable this default order on OBIEE to bring the default table order (as the rows were inserted).
I appreciate your help,
Thanks.

Hi Saichand,
Thanks for your answers.
I've uncked the ORDERBY_SUPPORTED feature, restarted BI Server and Presentation. My report does not have any column flagged to sort, even thought it still applying an order by clause in the SQL Statement. I went to the Advanced tab on Answers I can see the order clause in the SQL statement and this is the log generated by the query:
+++Administrator:2b0000:2b0018:----2010-10-14 09:44:21
-------------------- Logical Request (before navigation):
RqList
INPUT.INPOBK as c1 GB,
INPUT.INPBNK as c2 GB,
INPDRA:[DAggr(INPUT.INPDRA by [ INPUT.INPOBK, INPUT.INPBNK, INPUT.INPTDS, INPUT.INPKBT, INPUT.INPKSQ, INPUT.INPUID, case INPUT.INPTDS when ' ' then ' ' else case when INPUT.INPUID like '%GIFTS%' then '0' else '1' end end , case INPUT.INPKBT when '0' then '0' else INPUT.INPBNK end , INPUT.INPOBK || ' ' || INPUT.INPBNK] )] as c3 GB,
INPCR1:[DAggr(INPUT.INPCR1 by [ INPUT.INPOBK, INPUT.INPBNK, INPUT.INPTDS, INPUT.INPKBT, INPUT.INPKSQ, INPUT.INPUID, case INPUT.INPTDS when ' ' then ' ' else case when INPUT.INPUID like '%GIFTS%' then '0' else '1' end end , case INPUT.INPKBT when '0' then '0' else INPUT.INPBNK end , INPUT.INPOBK || ' ' || INPUT.INPBNK] )] as c4 GB,
INPUT.INPTDS as c5 GB,
INPUT.INPKBT as c6 GB,
INPUT.INPUID as c7 GB,
case INPUT.INPKBT when '0' then '0' else INPUT.INPBNK end as c8 GB,
INPUT.INPOBK || ' ' || INPUT.INPBNK as c9 GB,
case cast(INPUT.INPKBT as INTEGER ) when 0 then 0 else INPDRA:[DAggr(INPUT.INPDRA by [ INPUT.INPOBK, INPUT.INPBNK, INPUT.INPTDS, INPUT.INPKBT, INPUT.INPKSQ, INPUT.INPUID, case INPUT.INPTDS when ' ' then ' ' else case when INPUT.INPUID like '%GIFTS%' then '0' else '1' end end , case INPUT.INPKBT when '0' then '0' else INPUT.INPBNK end , INPUT.INPOBK || ' ' || INPUT.INPBNK] )] end as c10 GB,
case cast(INPUT.INPKBT as INTEGER ) when 0 then 0 else INPCR1:[DAggr(INPUT.INPCR1 by [ INPUT.INPOBK, INPUT.INPBNK, INPUT.INPTDS, INPUT.INPKBT, INPUT.INPKSQ, INPUT.INPUID, case INPUT.INPTDS when ' ' then ' ' else case when INPUT.INPUID like '%GIFTS%' then '0' else '1' end end , case INPUT.INPKBT when '0' then '0' else INPUT.INPBNK end , INPUT.INPOBK || ' ' || INPUT.INPBNK] )] end as c11 GB,
case INPUT.INPTDS when ' ' then ' ' else case when INPUT.INPUID like '%GIFTS%' then '0' else '1' end end as c12 GB,
INPUT.INPKBT as c13 GB,
INPUT.INPKSQ as c14 GB,
Report_Sum(INPDRA:[DAggr(INPUT.INPDRA by [ INPUT.INPOBK, INPUT.INPBNK, INPUT.INPTDS, INPUT.INPKBT, INPUT.INPKSQ, INPUT.INPUID, case INPUT.INPTDS when ' ' then ' ' else case when INPUT.INPUID like '%GIFTS%' then '0' else '1' end end , case INPUT.INPKBT when '0' then '0' else INPUT.INPBNK end , INPUT.INPOBK || ' ' || INPUT.INPBNK] )] by [ ] at_distinct [ INPUT.INPOBK, INPUT.INPBNK, INPUT.INPTDS, INPUT.INPKBT, INPUT.INPKSQ, INPUT.INPUID, case INPUT.INPTDS when ' ' then ' ' else case when INPUT.INPUID like '%GIFTS%' then '0' else '1' end end , case INPUT.INPKBT when '0' then '0' else INPUT.INPBNK end , INPUT.INPOBK || ' ' || INPUT.INPBNK] ) as c15 GB,
Report_Sum(INPCR1:[DAggr(INPUT.INPCR1 by [ INPUT.INPOBK, INPUT.INPBNK, INPUT.INPTDS, INPUT.INPKBT, INPUT.INPKSQ, INPUT.INPUID, case INPUT.INPTDS when ' ' then ' ' else case when INPUT.INPUID like '%GIFTS%' then '0' else '1' end end , case INPUT.INPKBT when '0' then '0' else INPUT.INPBNK end , INPUT.INPOBK || ' ' || INPUT.INPBNK] )] by [ ] at_distinct [ INPUT.INPOBK, INPUT.INPBNK, INPUT.INPTDS, INPUT.INPKBT, INPUT.INPKSQ, INPUT.INPUID, case INPUT.INPTDS when ' ' then ' ' else case when INPUT.INPUID like '%GIFTS%' then '0' else '1' end end , case INPUT.INPKBT when '0' then '0' else INPUT.INPBNK end , INPUT.INPOBK || ' ' || INPUT.INPBNK] ) as c16 GB,
case cast(INPUT.INPKBT as INTEGER ) when 0 then 0 else max(INPDRA:[DAggr(INPUT.INPDRA by [ ] )] by [ ] at_distinct [ ] ) end as c17 GB,
case cast(INPUT.INPKBT as INTEGER ) when 0 then 0 else max(INPCR1:[DAggr(INPUT.INPCR1 by [ ] )] by [ ] at_distinct [ ] ) end as c18 GB
DetailFilter: INPUT.INPOBK <> INPUT.INPBNK
OrderBy: c1 asc, c2 asc, c5 asc, c6 asc, c7 asc, c8 asc, c9 asc, c12 asc, c6 asc, c14 asc
+++Administrator:2b0000:2b0018:----2010-10-14 09:44:21
It seems that OBIEE did not remove the "order by" as expected.
Can you please let me know how to force OBIEE to do not use the order by clause?
Thanks,
Danilo

Removing the Order from Campaign in /SAPAPO/CDPS_FDISHEU, but it is not reflecting in DS_ board.

Hello Experts,
we wan to create some custom logic to Remove some orders from campaign. For this we have created a function and removing the order from campaign in /SAPAPO/CDPS_FDISHEU->BEFORE method.
but the changes which i am doing they get save immediately in DB (Without press Save from DS board).
and also they are not getting reflected in DS Board also.
Please let me know, If you need any further information to help me out.
Thanks in Advance
Ashish Gupta

Hello Experts,
Any clue will help, please suggest.
Thanks,
Ashish Gupta

Availibility check not happening after credit block is removed for order

Hi All,
When we are removing the credit block on a sales order through report RVKRED09, the availibility check is not performed again because the qty in sales order is not confirmed.
As per my understanding when the report RVKRED09 is run, the sales order is called in background and the credit status is changed and then subsequently, the user exit MV45AFZF is called. In this exit, the values in wa-ybuk-cmgst is compared against wa-xbuk-cmgst. if i think wa-ybuk-cmgst is A and wa-xbuk-cmgst is B, then it means the credit blocked is removed and the return code is 8 which means availibility check is to be performed.
However in our case availibility check is not happening since the values of wa-ybuk-cmgst and wa-xbuk-cmgst are same which is B i..e the credit block is not removed...but however the report RVKRED09 shows that cedit status is changed.
Something is happening somwhere which is causing this. could any one guide. Also what is the program name which confirms the availibility check in sales order and also what is the program name which changes the credit status for a sales order in VBUK table.
regards
sachin

Hi
So as per your query , you have gone with the user exit in the program MV45AFZF , so check wheather any subprogram has been included where availability check wont happen.So just take the help of ABAP;er and then check wheather any program has been included related to availability check.
Regards
Srinath

ATP Orders deletion

Hi All,
I tried to delete the ATP order of one single product through program /sapapo/sdorder_del. But its not deleting.
I checked the same order in va03 of R/3 system to check whether any product having the same ATP orders and i got 3 products.
Then i checked these 3 products in WUF in APO system to check whether any LC orders are linked to the ATP order (which i want to delete).
I got the 2 LC orders..
Do i need to delete this LC orders first?
So please help out in deleting the ATP order.
With Regards,
Santosh G C

Hi Santosh,
Did you tried with tab "Delete from liveCache and Database", i believe you don't need to delete any LC order for deleting these orders.
If you know order nos. (i think you can get order nos. from ECC easily), with that you can make selection via document no..
Hope this helps.
Other way is to remove the product from sales order integration model.
Run CCR fro this product and you will get all orders for this product, you have the option to delete them from APO, try this if /sapapo/sdorder_del doesn't work.
Rgds
Sourabh

"Delete on Database" in /SAPAPO/SDORDER_DEL

Dear All,
Can somebody help explain what happens when we execute "Delete on Database" in /SAPAPO/SDORDER_DEL? and how would the program acts for each selection parameters, if;
- we have not put anything in the selective deletion portion of the screen for "Location", "Product", and "Last Changed Before" fields, don't tick the check box for "Without check" option; but tick the check boxes for "Adjust ATP tables with /SAPAPO/POSMAPN table" and "Delete Obsolete Records in the /SAPAPO/POSMAPN table" in the additional function, what will happen? Will it delete anything? Or will it only do as what the additional function says?
- how about in the product allocation data portion, considering that we have specified a location, what is being deleted when the check box for "Delete Product Allocations" is ticked? and what is being done if the check box for "Check Product Allocation Assignment" is ticked?
Thanks in advance for any response.
Regards,
Philip

Dear Philip,
Find below few points about this transaction.
1. check is normally carried out before an order is deleted to see if this order still exists in liveCache. If this is the case, the order is not deleted.
2. You can also print out a list of the orders that cannot be deleted if you have set the relevant indicator.
3. In exceptional cases, you can deactivate this check and nevertheless still delete the selected orders.
4. If you have set the Delete all orders indicator, the order data from the database is completely deleted without any check. You should take great care when using this function.
5. A location product or a location can only be deleted if SD sales documents for this location product no longer exist in the database (that is, if, for example, no more entries exist in the tables /SAPAPO/ORDADM_I or /SAPAPO/ORDPART).
Regards,
Siva.

Inputs for running /SAPAPO/SDORDER_DEL report

Hello,
We want to run /SAPAPO/SDORDER_DEL report to delete unnecessary Sales orders in the APO system. Before while executing this report I would like to be clear on 2 points:
1. Three tabs with various fields came up after executing this report:
    1.Delete on Database
    2.Delete in SAP livecache and Database
    3. Delete All DB Sales Order data
Can someone please let me know the major differences of these tabs or any advantages or disadvantages of using one over the other.
2. Second point I want to understand is that, once I delete Sales Order data is using this report there any way, I could retrieve that data back.
Your thoughts and suggestions are very much appreciated.
Thanks,
Venkat.

Hi Venkat,
In APO you have information in two instances a database and a livecache.
With the first tap you can delete obsolete entries that exist in database, but they are not in livecache. Here you have additional options to delete allocation objects from ATP and delete and adjust ATP tables.
Second tab is to delete orders from livecache using different selection parameters.
Third tab is to delete all order from the database.
So first is to adjust ATP orders on database, second on livecache and third to delete all.
As i know, you can not retrieve information of this tables after running this report.
I hope this can help you.
Regards.
Marín.

Issue while running Report /SAPAPO/SDORDER_DEL

Hello All,
We are using the first tab "Delete on database" in the Report /SAPAPO/SDORDER_DEL. We have created a variant with a combination of selections like "Locations" and "Last before change date" and also we checked the addtional functions "Compare ATP tables with /SAPAPO/POSMAPN" and "Delete Obsolete records in /SAPAPO/POSMAPN".
The issue we faced is that, elements like sales orders, deliveries and Purchase orders are deleted without considering the "locations" and "last changed before date". Elements of very recent date (09/08/2007) are deleted even though the "last changed before date" is somtime in the past (eg. 05/31/2007).
Can please someone let me know your ideas on this?
Thanks,
Venkat.

Hi Venkat,
You can check OSS note : 657214 /sapapo/sdorder_del: Documentation and usability.Note 553476 - Composite note: Report /sapapo/sdorder_del.
Best Regards,
Siva.

ATP order deletion ( orders exit only in APO)

Hi All,
I have to delete the ATP orders in APO and for that relevant sales order doesn't exit in R/3.
I tried with /SAPAPO/SDORDER_DEL and even i did the CCR for it. Its not deleting.
Pls suggest how to delete the order.
Regards,
Santosh G C

Hi,
You can do this by running CIF delta report or CCR. Choose delete in APO (but make sure that the orders are really not existing in R/3).
If CIF delta report or CCR will not work, you can try running report RLCDELETE and check if you can delete those orders. If RLCDELETE will not work and the system prompted a message that orders are not anymore exist in the LiveCache then, please let me know.
Thanks,
AA

Question while using report /SAPAPO/SDORDER_DEL

Hello all,
While using Report /SAPAPO/SDORDER_DEL and going through system documentation, I found that:
"Normally, the order data remains in the database (it is not deleted as in live Cache)."
From the above statement I am assuming that data gets deleted in live cache on a timely basis, Can someone please let me know how frequently the data gets deleted in live cache?
Thanks for your time,
Venkat.

Hi Venkat,
There is no specific frequency for data getting deleted from the live cache.
It depend on the transactions which are taking place in R3 and APO.
For eg. Sales orders create a requirement in the R3 which is transferred to APO.
Now when this sales order is delivered, the requirements gets deleted from R3 and similarly from APO livecache. But this information does not get deleted from the APO database tables.
So this report is used to delete R3 document data that is no longer required in APO.
Cleaning of the database tables in APO leads to better performance.
So as a best practice, this report should be scheduled to run weekly.
Regards,
Asheesh Gupta
Message was edited by:
asheesh gupta

/SAPAPO/SDORDER_DEL and /SAPAPO/SDRQCR21

Hello Experts,
Can some one give me the quick view on what these programmes do in APO from the business prospective...
Thanks
Venu

Dear Venu,
/SAPAPO/SDORDER_DEL: Delete (SD) Orders from APO database SD sales document data from the APO database are not deleted automatically as in liveCache. In order to delete these, it is necessary to run a deletion report. In order to limit the data volume, you should schedule the report to delete the orders, if necessary, and it should be dependent on the lifetime of your orders.
Please check following notes:
546459: /sapapo/sdorder_del: Performance and recommendations
504620: Deletion of R/3 data that are no longer required in APO (/SAPAPO/SDORDER_DEL)
894294: /sapapo/sdorder_del: Performance and advice (as of SCM 4.0)
705901: /SAPAPO/SDORDER_DEL: New selection screen (as of SCM 4.0)
/SAPAPO/SDRQCR21: This report corrects incorrect sales order and delivery (requirements) in SAP R/3 / ECC and SAP. APO/SCM and checks precisely the SD order tables but doesn't check inactive integration models.
Please check the note 444641 for /sapapo/sdrqcr21
I hope I could help you.
Regards,
Tibor

Delete entries in /SAPAPO/POSMAPN with /SAPAPO/SDORDER_DEL

Hi Guys,
we´re having many orders in table //POSMAPN that are not existing in liveCache.
We assume that these are obsolete orders that can be deleted with report //SDORDER_DEL.
My question:
What is the prerequisite for orders being deleted from //POSMAPN with //SDORDER_DEL?
Or in other words: Which entries in //POSMAPN are considered as "obsolete" by //SDORDER_DEL?
Thanks a lot for your help.
Andreas

Hello Andreas,
When you run the /SAPAPO/SDORDER_DEL program, you should run the program to delete the orders from both Live Cache and Database ( see the 2nd tab on the selection screen of this program). This way you can ensure that it is deleted properly. Otherwise, when you run //CCR or //SDRQCR21 it only checks the livecache. Since, it has already been deleted in your case, you can give it a try to see if you can delete the orders from DB using option "Delete from DB" ( see the 1st tab).
Also, usually the order gets disappeared from LC once the order is PGIed, however a bit of information is still available on APO side and thats where this program would delete it to counter that. The reason why the order line info is still stored in APO is due to the fact that the order lines can always be reverse PGIed and the delivery can also be deleted. So, it is a wise option to run this program by providing the Period in the selection screen which is usually the MBDAT and as a regular practice you can provide a date range that is less than 90 days or so.
Hope this helps
Babu Kilari

Message in /SAPAPO/SDORDER_DEL

Dear all,
When running the /SAPAPO/SDORDER_DEL program we get the message: prod. xxx, vers: 000 orders exist (use report: /sapapo/rlcdelete)
In /sapapo/rlcdelete for this product I see 2 orders.
The difference with orders I can delete is that the Cat, Product,Location, lst.Ch.on and Chk.SDord is not showing any values.
Any clues to solve this in APO 4.0?
Cheers

Hi ,
Please run the consistency check report :
1. /SAPAPO/OM17 consistency check
2. Planning area consistency check through program /SAPAPO/TS_LCM_CONS_CHECK.
3. CCR
check weather order is availabe in RRP2, RRP3.
than try to delete it again by RLCDEL.
Manish

4-4-5-Error-Financial year variant periods K5 are not in increasing order

Hi,
As per the client requirement I have to configure the Posting Periods in the Calender Year
Month     Posting Period     Days in the period          From     To
January     1     31     1                                  1-Jan-09     31-Jan-09
February     2     28     2                                  1-Feb-09     28-Feb-09
March     3     35     3                                  1-Mar-09     4-Apr-09
April     4     28     4                                  5-Apr-09     2-May-09
May     5     28     5                                  3-May-09     30-May-09
June     6     35     6                                  31-May-09     4-Jul-09
July     7     28     7                                  5-Jul-09     1-Aug-09
August     8     28     8                                  2-Aug-09     29-Aug-09
Septem     9     35     9                                  30-Aug-09     3-Oct-09
October     10     28     10                                   4-Oct-09     31-Oct-09
Novem     11     28     11                                   1-Nov-09     28-Nov-09
Decemb     12     33     12                                  29-Nov-09     31-Dec-09
As per this requirement I have configured the following
1. Copied F/Y variant K4 to K5
2. Made the following settings
month     Days     Period
1     31     1
2     28     2
3     31     3
4     4     3
4     30     4
5     2     4
5     30     5
5     31     6
6     30     6
7     4     6
7     31     7
8     1     7
8     29     8
8     31     9
9     30     9
10     3     9
10     31     10
11     28     11
11     30     12
12     31     12
When I save this setting the following error is given
Financial year variant periods K5 are not in increasing order
Message no. FGV555
Diagnosis
The posting periods are not in ascending order.
Procedure
Specify the posting periods with the calendar year in ascending order
Request you to please let me know if there is a solution.
Regards,
Ambuj
+919739976912

Ambuj,
In your settings for fiscal year variant K5, you do not need the following entries:
3     31     3
4     30     4
5     31     6
6     30     6
7     31     7
8     31     9
9     30     9
10     31     10
11     30     12
Please try removing these entries and see if that resolves the error.
You only need to account for the last day of the calendar year (12/31/xxxx). You do not need to account for the last day of every calendar month. As a result, you do not need entries for the last days of January - November, unless the last day of the month is also the last day of the period, as is the case for your periods 1 and 2. That is why the entries for the entries for 1/31 and 2/28 are OK, but the other calendar month end entries should be removed.
Regards,
Shannon

Cash discount calculation at invoice level not at sales order level

Dear Friends
while i am executing the sales cycle creten Cash discount conditions are calculating in the Invoice directly not in sales order.
can you please let us know your views oin what basis iot calculating directly in the invoice, since payment terms is there in both sales order and invoice level. but discount is only appearing at invoice level, not in the sale order level..
where these setting incurred in this process. i have verifies all the routies, there is no such kind of logic to calculate in a particular palce.
treat this one as high priority and let me know.
Thanks
Raju.

Hi
while i am executing the sales cycle creten Cash discount conditions are calculating in the Invoice directly not in sales order.
can you please let us know your views oin what basis iot calculating directly in the invoice, since payment terms is there in both sales order and invoice level. but discount is only appearing at invoice level, not in the sale order level..
Please check your Pricing Procedure, whetehr against your Cash Discount Condition Type, Requirement 24 or 23 is maintained? If it is maintained remove these requirements and save. Then try to run the transaction.
Regards,
Amitesh Anand

/SAPAPO/SDORDER_DEL not removing ATP orders

Similar Messages

Maybe you are looking for