2lis_11_v_ssl extractor and behaviour with rush orders

Hi All,
I hope someone can help us with this issue.
We have standard sap extractor 2lis_11_v_ssl which pulls data into BI 7.0 into the PSA and then onto a dso (all v7 functionality).
For standard sales orders, all works perfectly. However, for rush sales orders we have issues.
The target DSO has as it's key sales order, sales order item, delivery and delivery item.
For a normal sales order in the delta queue we see the following sequence of records:
1) Sales Order Creation (only sales order and sales order item key parts filled)
2) Delivery Creation (sales order, sales order item, delivery and delivery item key parts filled)
3) Sales Order Creation cancellation image (sales order and sales order item filled and rec_deleted = X)
In the DSO we end up with 2 records - basically records 2 and 3. In our reports we use the rec_deleted flag = X to ignore those records.
For a rush sales order, the records end up in the delta queue in a different order. I presume this is because on sales order save, both the sales order and delivery are created at the same time - presumably the delivery save process completing first? We see this:
1) Sales Order Creation cancellation image (sales order and sales order item filled and rec_deleted = X)
2) Sales Order Creation (only sales order and sales order item key parts filled)
3) Delivery Creation (sales order, sales order item, delivery and delivery item key parts filled)
In our DSO, we end up with records 2 and 3 again - BUT - the rec_deleted flag = X from record 1 has been overwritten. This means the records are no longer ignored in our reports and we have double counting on several key figures (confirmed qty etc).
Has anyone seen this before? Can anyone suggest any ways in which we can solve this?
Many thanks in advance.
Mark

Magesh,
We have no code in the start routines to deal with the images.
We did think about this, but we could never be sure as to what data came in on the source packages from R3 (eg if there was an update delay etc).
By changing the rules in the DSO to summation from overwrite this issue is completely resolved.
Regards,
Mark

Similar Messages

How do I keep watermarks and presets ( with their order ) synched between computers

I have a desktop which I use for heavy picture editing and a mac book air that I use for on the fly picture editing to show clients during photo trips.
I want to figure out a way for keeping my watermarks and presets ( with their order and folders I created on my desktop ) synched on my laptop.
What is the best way of doing this? If keeping it synched is not possible, how do you advise importing them to my laptop?
Thanks for the support,
JP Jacobsen

Ps: It is very important that the presets come on the same order and folders I re-arranged them in my desktop.

Problems and Issues with Internal Order Transactions

Hello I have a couple of problems with Internal Order Transactons.
Its strange really, when I simulate in the development server. I do the following process:
Assign Asset with IO -> Create PR with account assignment to an Asset -> Create PO with Reference to PR -> Create GR.
Once this occurs, the transaction seems to reflect in particular reports such as List: Order by Cost Element, List: Budget/Actual/Commitments, etc.
But when another user does a similar process in PRD, it doesnt seem to reflect in these reports.
Also while, I cant seem to pass the GR if the Internal Order has not been released. The user was able to create a GR whose IO has not been released yet.
These problems are quite striking to me. Does anyone know the possible causes of the situations at hand? Any feedback will be most helpful.
Thank you all and good day.

Ok never mind, seems I found the culprit (though the reason gives more questions than answers)! Thanks anyways

Error in Rush Order type with BOM item!!

Hello,
I am facing a very strange error while creating a rush Order with BOM item.
System Error:
1. No item category available (Table T184 SO ERLA TAQ).
I except the error. I get next error as
2. Structure explosion for item 000010 is not possible.
After this BOM explodes with only first 2 Sub Items ( Item cat for main item is determind as TAQ and Sub Items as TAE) , where as the complete BOM has 7 Sub items.
I have made the required configs in item cat determination in T184 table for order type SO, as follows.
SO ERLA - TAQ for Main Item of the BOM
SO NORM TAQ TAE for the Sub Item of the BOM
The same item (BOM ) works very well in OR/BV kind of sales order types, by exploding the BOM to full level(i.e all the 7 sub items are determined).
Has any one come across such an issue. Please let me know what could be the solution?
Thanks in adv,
Shripad

Hi,
Thanks,
In vov7 for TAQ Item Cat. the structure scope is maintained as 'A'. And that's the reason for Standard order 'OR' , the BOM is exploding properly.
It is only with Rush Order , the BOM is not exploding correctly.
BR
Shripad

BOM error in Rush Order.

Hello,
I am facing a very strange error while creating a rush Order with BOM item.
System Error:
1. No item category available (Table T184 SO ERLA TAQ).
I except the error. I get next error as
2. Structure explosion for item 000010 is not possible.
After this BOM explodes with only first 2 Sub Items ( Item cat for main item is determind as TAQ and Sub Items as TAE) , where as the complete BOM has 7 Sub items.
I have made the required configs in item cat determination in T184 table for order type SO, as follows.
SO ERLA - TAQ for Main Item of the BOM
SO NORM TAQ TAE for the Sub Item of the BOM
The same item (BOM ) works very well in OR/BV kind of sales order types, by exploding the BOM to full level(i.e all the 7 sub items are determined).
Has any one come across such an issue. Please let me know what could be the solution.
Thanks in adv,
Shripad

Hi,
Thanks,
In vov7 for TAQ Item Cat. the structure scope is maintained as 'A'. And that's the reason for Standard order 'OR' , the BOM is exploding properly.
It is only with Rush Order , the BOM is not exploding correctly.
BR
Shripad

Acrobat Forms: "Rush Order" Button

How do I create a button that shows the image "Rush Order" when clicked and hides the image when clicked a second time?
So far I have figured that I need three buttons to acomplish this...
One button that is hidden and has the "Rush Order" image shown on "up".
One button to show the "Rush Order" image button.
One button to hide the "Rush Order" image button.
It's odd that I can't have a button with an icon that becomes visable when clicked and stays visable untill clicked a second time.
Anyone know how to do this easily without three buttons?
Thank You!
Jeremy

2 buttons are certainly enough. Let's say the image button is called "Image". Then you use this code as the other button's MouseUp Run a JavaScript code:
var f = this.getField("Image");
f.display = f.display==display.visible ? display.hidden : display.visible;
That's it...

Scarp update to SL with Prd order -Confirmation

We are doing Rejection Scrap updation with 501 movt type - Plant - SL - refernce with Order (Order filed is made mandatory in display settings)
(Scrap generated unplanned while doing production process).
Now the new requirement came like , according to confirmation process - unplanned scrap will get generated and Business want to do MB!C-501 with Confirmation and not with Order.(But confirmation field is not available in option Displat screen layout )
Kindly suggect how to proceed

In Production Process - Two type sof scrap generate
1. planned - which is maintained in BOm and update with 531 mvt type
2. Unplanned - which is booked in scrap field while doing Confirmation. Suppose my Order material broke on the way/while doing maching etc . ( No where found in Inventory)
here case 2 , that scrap mat F is also sold . So an alternative method mentioned was with 501 will update scrap material and ref made as Prd Order Number(order mat Y).
It is fine , some how it meets the business req.BUt now they want with ref to confirmation But confrimation field is not avilable in Display screen for 501.
I know 501 is not for this , but for the business [purpose it was mapped like this .
551 will update o cost centre and not in INV
So kindly help me to upload the scrap with 501 with Production confirmation and not with Production Order
Edited by: manu m on Apr 27, 2010 5:52 AM

Diff between with production orders

Hi Friends,
pls explain dif between planned orders & Production orders.
Regards
Jagadeeshwar.B

Hi,
Planned orders are results of running MRP. Shortages of materials that are set to internal procurement will create planned orders, which can be converted into production orders. Production orders are like "hard copies", they cannot be adjusted by MRP anymore. Well that's for a discrete environment, not sure about repetitive manufacturing.
One we firm the planned order changes will be not reflected in the subsequent MRP, correct. e.g. BOM change. New components will not be recommended for firm planned order.
I'm assuming when you ask about when to use planned vs production orders you are asking when to use Repetitive Mfg (with PE planned orders) vs Discrete Mfg (with production orders). We use both and while we're not perfect in our approach yet we are gaining a better appreciation for the two.
For repetitive, the planning is much simpler, you basically run MRP against your demand and you get planned orders. You can change and firm these manually or you can use time fence strategies, and you can have multiple operations running through multiple work centres. They are very simple to maintain and use. Repetitive is normally run against shorter lead time build, where we don't need a high level of control. If we have the option we go with Repetitive.
Where we want a better level of control we go with discrete. Planned (LA) orders are created from a run of MRP against your demand. These are converted to production orders, released, and processed. There is a lot more control (and work) with this order type than we see with Repetitive planned orders. We can link documents to the order, we can change the routing and the BOM on the order, and we have better visibility of the individual orders while they are in manufacturing. Costing is against the order as opposed to Repetitive where the costs (and variances) are seen against the cost collector. After everything is complete, you still have a record against the build. The order stays intact, though it may be complete and closed, you still the retain history.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Standard Rush Order with multiple plants

Hello gurus,
We just upgraded to 6.0 from 31I and when creating a
rush order with multiple plants the first item's delivery
does not contain a ship-to party were the second item's
delivery does. Table VBPA does not have a record for the
first delivery but the second delivery is there. This did not happen in 31I.
Please advice.
Best Regards.

hello, Ruben.
hhmmm. your table XVBPA looks like a created table that is not SAP standard. i am not an ABAP person so i could not pretend to give you good advice, but i (my speculation only) suspect that there was a user exit or an ABAP program that made the system do the postings to this table instead of the standard VBPA.
i further speculate that during the upgrades, some of the enhancements may have been lost or diverted. (to prevent this, you usually use the 'Z' naming convention, which is to have this letter as the start of any name for an enhancement or definition outside of SAP standard)
your best bet is to try getting an ABAP consultant (or are you one already?) to help you look at this.
regards!

Rush orders with third party delivery-?

Hi Gurus
I have seen the scenario -
Rush orders are creating third party sales .
Rush orders means Immidiate delivery will create and also in our configuraion same.
But third party item category measn delivery from vendor.
My question is how it possible-?
Please any body can give solution on this.
Thanks
Kris

pls under stand the deference between 3 party and rush order
rush order means immediate delivery created when you save the sales order ( where you have the stock and you are going to service it )
3 party means where the 3 person is going to service the material with reference to your sales order that is
your sales order triggers a purchase reg and converted to PO and the 3 party vendor supply material to you and you supply to the orderd person
so it is not a correct process to have a rush order in 3 party processing

Difference betwen cash sales and rush order

hai members
pl mail me the diff bet Cash Sales And Rush Order
and there implication in Billing documents.
mail me to: [email protected]

<b>Rush Order</b>
In a rush order, the customer picks up the goods immediately, or you deliver them on the same day as when the order was created. When you save the rush order, a delivery is automatically created in the standard system. Billing the rush order takes place as normal, after the delivery.
In the standard system, sales document type RO is saved for rush orders with immediate delivery type LF. Once the goods have been removed from storage, the goods are picked, and goods issue is posted.
Once the billing documents are created (for example, in collective processing), invoice papers are printed and sent to the customer.
IN IMG-SD-SALES-SALES DOCUMENT HEADER-ORDER TYPE RO/CS U CAN SET A FOR IMMEDIATE DELIVERY IN SHIPPING WHICH CREATES DELIVERY AUTOMATICALLY WHEN U SAVE SALES ORDER
<b>Cash Sales</b>
In cash sales, you can process an order for when the customer orders the goods, picks them up, and pays for them immediately. The delivery is processed at the same time as when the order is created and a cash invoice is printed immediately: billing is therefore related to the order, unlike rush and standard orders. Receivables are not created for the customer, as they are for rush and standard orders because the amount in the invoice is immediately posted to a cash account.
In the standard system, sales document type BV (CS) is saved for cash sales with immediate delivery type BV.
When the sales employee creates a cash sale, the system automatically proposes the current date as the date for delivery and billing. Once the order has been posted, a delivery with type BV is created immediately in the background and the system prints a document that is used as an invoice for the customer.
The invoice papers are controlled with output type RD03, contained in the output determination procedure for order type CS.
Regards,
Rajesh Banka
Reward suitable points.
How to give points: Mark your thread as a question while creating it. In the answers you get, you can assign the points by clicking on the stars to the left. You also get a point yourself for rewarding (one per thread).

Cash sales and Rush order

What is the difference between Cash Sale & Rush Order?

Hi
Cash Sales: In this type of order CS, as soon as you save the sales order the delivery is automatically created as same date and billing will also be generated at the same date as soon as you save the delivery document.
In a rush order, the customer picks up the goods immediately, or you deliver them on the same day as when the order was created. When you save the rush order, a delivery is automatically created in the standard system. Billing the rush order takes place as normal, after the delivery.
In the standard system, sales document type RO is saved for rush orders with immediate delivery type LF. Once the goods have been removed from storage, the goods are picked, and goods issue is posted. Once the billing documents are created (for example, in collective processing), invoice papers are printed and sent to the customer.
Rush Order: In this type of Order RO , The delivery will be created as soon as you save the sales order. But you bill the customer later.
In cash sales, you can process an order for when the customer orders the goods, picks them up, and pays for them immediately. The delivery is processed at the same time as when the order is created and a cash invoice is printed immediately: billing is therefore related to the order, unlike rush and standard orders. Receivables are not created for the customer, as they are for rush and standard orders because the amount in the invoice is immediately posted to a cash account.
In the standard system, sales document type BV (CS) is saved for cash sales with immediate delivery type BV.
When the sales employee creates a cash sale, the system automatically proposes the current date as the date for delivery and billing. Once the order has been posted, a delivery with type BV is created immediately in the background and the system prints a document that is used as an invoice for the customer. The invoice papers are controlled with output type RD03, contained in the output determination procedure for order type CS.

Cash sale and rush order

what's the differnce between cash sales and rush order?

HI
In case of cash sales the billing document is generated immediately after the order is saved.
In case of rush order,delivery will be created immediately.
In a rush order, the customer picks up the goods immediately, or you deliver them on the same day as when the order was created. When you save the rush order, a delivery is automatically created in the standard system. Billing the rush order takes place as normal, after the delivery.
In the standard system, sales document type RO is saved for rush orders with immediate delivery type LF. Once the goods have been removed from storage, the goods are picked, and goods issue is posted.
Once the billing documents are created (for example, in collective processing), invoice papers are printed and sent to the customer.
IN IMG-SD-SALES-SALES DOCUMENT HEADER-ORDER TYPE RO/CS U CAN SET A FOR IMMEDIATE DELIVERY IN SHIPPING WHICH CREATES DELIVERY AUTOMATICALLY WHEN U SAVE SALES ORDER
Cash Sales
In cash sales, you can process an order for when the customer orders the goods, picks them up, and pays for them immediately. The delivery is processed at the same time as when the order is created and a cash invoice is printed immediately: billing is therefore related to the order, unlike rush and standard orders. Receivables are not created for the customer, as they are for rush and standard orders because the amount in the invoice is immediately posted to a cash account.
In the standard system, sales document type BV (CS) is saved for cash sales with immediate delivery type BV.
When the sales employee creates a cash sale, the system automatically proposes the current date as the date for delivery and billing. Once the order has been posted, a delivery with type BV is created immediately in the background and the system prints a document that is used as an invoice for the customer.
The invoice papers are controlled with output type RD03, contained in the output determination procedure for order type CS.
Differences:
1.order type is :CS--RO.
2.Item category: BVN--TAN
3.no credit active in case of cash sale at item category level.
4.output type in cash sale:RD00.
5.account key--EVV(cash sale).
In cash sales the std sap sales doc type is CS, item category is BVN and Schedule line category is cp. Here when you are creating cash sales order system won't search for credit limits and once cash sales order is created system in background create delivery also .Here we are using a Separate Account key EVV and for output we are using RD03.In cash sales del type is BV, billing type is BV.
In Rush orders the std sales doc type is RO, item category is TAN, Schedule line category is CP. dely type id LF, billing type is F2,output type RD00 here in rush sales order system in background will create delivery and it will check credit limit of the customer
Scenario of Cash Sales and Rush Order
Message was edited by:
SHESAGIRI.G

Difference Between Cahs Sales, Rush Order and Standard Order

Hi gurus,
I want to know whole configration for rush order and difference between 1. Rush order and cash sales. 2. cash sales and standard order.
Would u please help me for this...
Regards
Prashant.

Hi,
1) Cash sale : in this delivery automatically happen when you save the sales order. After that you have to give an invoice to the customer.
2) Rush order. Here also delivery automatically happen when you save the sales order. But the difference is you can send invoice after some time but the delivery should happen immidately.
If you goto any super market first, you pick up the item and then pay the bill and then you will get the bill, this process is cash sales.
Cash sales is order related billing whereas RO is delivery related.
Cash sales is not relevant for availability check as you will be picking the goods whereas RO is relevant for availability check.
Cash sales is also not relevant for credit management whereas RO is relevant credit management.
Cash sales uses RD03 as output which immediately prints the invoice whereas RO uses standard output RD00.
Cash sales has one time customer account group where as RO normally doesn't.
For cash sales order type is BV or CS and for RO it is RO
Cash sales triggers petty cash a/c where as in RO customers account is debited.
Delivery and settlement will be done immediately in cash sales where as in RO only delivery will be done immediatrly.
Rush Order/Cash Sales u2013
Rush orders and Cash sales are sales document types that are used in the sales from plant process or when the customer needs to pick their goods immediately from the warehouse.
In the sales document type, the following changes have to be made for rush order/cash sales u2013
a. order type u2013 RO/CS
b. shipping conditions u2013 immediately
c. immediate delivery u2013 X
d. lead time in days u2013 not to be specified
e. delivery type u2013 LF/BV
f. billing type u2013 F2/BV
g. item category u2013 TAN/BVN
h. schedule line category u2013 CP/CP
In case of rush orders and cash sales once the goods have been withdrawn from the warehouse, picking and posting goods issue can begin.
In case of rush orders, when you create the billing documents the system prints the invoice papers and sends them to the customer.
But in case of cash sales, an order related billing index is generated automatically. This updates the billing due list. Billing type BV is created, while the billing due list is being processed and the system does not print invoices during billing for a cash sale.
In cash sales when you save the order, the system automatically generates a cash receipt that can be given to the customer as an invoice and the goods are picked up from the warehouse immediately by the customer. You control the output with output type RD03, contained in the output determination procedure for order type CS.
Best Regards,
Amit

Opening and closing stock with sales order and with out sales order

hello,
any body please help me my client want to check opening stock and and closing stock in areport.
material contains batch and some material with sales order and some are with out sales order. my client is asking this in a single layout. please tell me isthere any teport or bapi or function module to get this report.
this is very uregent. and layout is requesting like opening stock, production stock, sales stock and closing stock.
please guide me to get this report.
Thanks & Regads
Bhakta

Transaction MB5B
For sales order related use specila stock as E and use radio button indicator in stock type
For stock w/o sales order, use special stock indiactor as "space' and stock type valuated stock.
to get a perticular month,opening stock/closing stock enter the start date/end date as month start and end date.
See the o/p which will give the stock as required by you

2lis_11_v_ssl extractor and behaviour with rush orders

Similar Messages

Maybe you are looking for