Batch Printing for Sales Orders

Hi all
Is it possible to have a batch printout job to be set to run on a certain time or just a script to run when you want to print sales orders based on date and on udf then print by selected criterias.
User Inputs.
+++ Date range +++
+++Route ID +++++
++++++++++
The print out must be done based on the Route selected in ascending order. The date is just for filtering.
Thanks.
Bongani

I don't believe we could write any scripts or set such a custom timer for selective printing based on Route.
The only option available for bulk printing is in Sales A/R > Document Printing... Sales Order
Suda

Similar Messages

Batch job for sales order

Hi,
How to create a job and schedule it so that it assigns reason of rejection to sales order line items for a particular sales org which are not delivered and after doing so, the status of the sales order is set to complete.
regards
sachin

Hi
Create a customised Z program with all the validations for the sales org, not delivered orders and assign this program to a batch job in SM36 which should run and sets the reason for rejection.
Regards

Problem submitting batch request for sales order creation

Hello experts,
I have created a gateway service, implementing the CREATE_DEEP_ENTITY for order creation. I have tested my service with the Chrome Advanced Rest Client and it works fine with the following XML request:
<?xml version="1.0" encoding="UTF-8"?>
<atom:entry xmlns:atom="http://www.w3.org/2005/Atom" xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices" xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
<atom:content type="application/xml">
<m:properties>
<d:OrderId>0</d:OrderId>
<d:DocumentType>TA</d:DocumentType>
<d:CustomerId>C6603</d:CustomerId>
<d:SalesOrg>S010</d:SalesOrg>
<d:DistChannel>01</d:DistChannel>
<d:Division>01</d:Division>
<d:DocumentDate m:null="true" />
<d:OrderValue m:null="true" />
<d:Currency m:null="true" />
</m:properties>
</atom:content>
<atom:link rel="http://schemas.microsoft.com/ado/2007/08/dataservices/related/SOItems" type="application/atom+xml;type=feed" title="SALESORDERTSCH.SOHeader_SOItems">
<m:inline>
<atom:feed>
<atom:entry>
<atom:content type="application/xml">
<m:properties>
<d:OrderId>0</d:OrderId>
<d:Item>000010</d:Item>
<d:Material>C20013</d:Material>
<d:Plant m:null="true" />
<d:Quantity m:Type="Edm.Decimal">100.000</d:Quantity>
<d:Description m:null="true" />
<d:UoM m:null="true" />
<d:Value m:null="true" />
</m:properties>
</atom:content>
</atom:entry>
<atom:entry>
<atom:content type="application/xml">
<m:properties>
<d:OrderId>0</d:OrderId>
<d:Item>000020</d:Item>
<d:Material>C20014</d:Material>
<d:Plant m:null="true" />
<d:Quantity m:Type="Edm.Decimal">200.000</d:Quantity>
<d:Description m:null="true" />
<d:UoM m:null="true" />
<d:Value m:null="true" />
</m:properties>
</atom:content>
</atom:entry>
</atom:feed>
</m:inline>
</atom:link>
</atom:entry>
Now that my service is working, I want to be able to call it from a SAP UI5/Javascript application. In order to process multiple items for one order header, I use the OData batch request. Here is my Javascript method that is being processed:
executeOrderCreation : function() {
// Retrieve model from controller
var oModel = sap.ui.getCore().getModel();
oModel.setHeaders(
{ "Access-Control-Allow-Origin" : "*",
"Content-Type": "application/x-www-form-urlencoded",
"X-CSRF-Token":"Fetch" }
// Define data to be created
var headerData = {
OrderId : "0",
DocumentType: "TA",
CustomerId : "C6603",
SalesOrg : "S010",
DistChannel : "01",
Division : "01",
DocumentDate : null,
OrderValue : null,
Currency : null,
varItemData1 = {
OrderId : "0",
Item : "000010",
Material : "C20013",
Plant : null,
Quantity : "100.000",
Description :null,
UoM :null,
Value :null,
varItemData2 = {
OrderId : "0",
Item : "000020",
Material : "C20014",
Plant : null,
Quantity : "100.000",
Description :null,
UoM :null,
Value :null,
var batchChanges = [];
oModel.refreshSecurityToken(function(oData, oResponse){
alert("Refresh token OK");
}, function() {
alert("Refresh token failed");
}, false);
oModel.read('/SOHeaders/?$Batch', null, null, false, function(oData, oResponse) {
// Create batch data
batchChanges.push(oModel.createBatchOperation("SOHeaders", "POST",headerData ));
batchChanges.push(oModel.createBatchOperation("SOHeaders", "POST",varItemData1 ));
batchChanges.push(oModel.createBatchOperation("SOHeaders", "POST",varItemData2 ));
oModel.addBatchChangeOperations(batchChanges);
// Submit changes and refresh the model
oModel.submitBatch(
function(oData) {
oModel.refresh();
function(oError) {
var error = oError;
alert("Read failed" + error);
false);
}, function() {
alert("Read failed");
The result is when I submit the batch, I have an error saying: The following problem occurred: no handler for data -
Am I doing right in the batchChanges creation ? (Header then items)
Why am I facing this error ?
Any help would be greatly appreciated.
Thanks and regards,
Thibault

Hi,
you should also have '/' before collection name so that it will be /SOHeader and as below.
batchChanges.push(oModel.createBatchOperation("/SOHeaders", "POST",headerData )); batchChanges.push(oModel.createBatchOperation("/SOHeaders", "POST",varItemData1 ));
batchChanges.push(oModel.createBatchOperation("/SOHeaders", "POST",varItemData2 ))
Regards,
Chandra

Print MULTIPLE sales order for a given date

Hi Gurus,
My requirement is to print sales order for a given date like the one given below.
VL71 - Output from Outbound Deliveries
VL74 - Output from Handling
VF31 - Output from Billing
VOK4- Output Determination: Inventory mgmt.
Is there any T.code for printng multiple sales order instead one-by-one printing using VA02/VA03?
Please hlep me in this regard.
Regards,
Anbu

Hi anbu,
This is very much possible to mass printing for sales orders.
Goto SE38 T.Code.
Enter the program name as "RSNAST00".
Press Execute or F8
Select output application as "V1" which is sales.
Enter your object key here.
Enter your output type.
Select the transaction medium as "1".
Tick "send again".
Press on Execute or "f8".
Regards,
Krishna.

Stock allocation for sales orders with batch job

Hi Friends
We have a batch job to allocate stock for sales orders which runs every week , currently this batch job is meant for plant 1000 with availability check procedure Z1 .
I need to incorporate for same batch job plant 1000 with availability check procedure Z2
Just I need to know that there is any potential impact and it causes any problem ?
Thanks In Advance
Rusheek

Hi,
Check what difference is between procedure Z1 and procedure Z2. As we cant see this, you will have to analyze what Z1 was doing and what Z2 is expected to do. Broadly speaking this is preety subjective to your project.
You analyze and try to find out the impacts. If needed take help of abaper.
Rgds,
SB

Standard print program & smart form for SALES ORDER

Hi,
I need
1. Print program &
2. SMART FORM
for "Sales Order".
and also please let me know how to migrate and do the required changes in smartform & print program.

Hi Sameer,
Goto NACE tcode-> choose the application u want( like billing for invoice, PO)->output type->output type->processing routineon left side
Here u will find the standard program name and smartform .
Thanks,
Reward If Helpful.

Default Batch value in sale Order items

Hello SD Experts,
Please, is there a way to recover a default value for the batch of all posts in a Sale Order (SO).
In fact I want to have a default value Z001 in the batch field of all post's of SO type ZS01.
is that possible? if so how the customiz it?
thank you in advance.
SDA

Hello,
You could consider creating a batch strategy (T-code VCH1) and use it to control the batch determination in sales order.
Hope it helps.
Regards,
Smile

Batch split in sales order

Hi,
I have a requirement as follows regarding the batch determination in sales order.
There is an item with 4 batches of 10 Qty each.
In the sales order the item is entered for 24 Qty, system is proposing 1st batch with 10 qty and the balance 14 is confirmed for a different date as no qty available for the stock as on today on the same batch.
But the stock is available with the other batch items meeting the selection criteria.
So can anyone let me know when the item is entered for 24, system should propose the available batches as 10 batch1, 10 batch2 and 4 for batch3 in sales order.
What is the setting required to be done for this scenario?
Thanks and Regards,
Gopinath Naik R

Hi,
Thanks for your reply.
But my requirement is exactly the one u have suggested and it goes like this,
Item A has three batches 00001111, 00002222, 00003333
00001111 - 12 Qty
00002222 - 15 Qty
00003333 - 10 Qty
When a sale order is created for 14, as per the selection criteria if the selection is as per the sequence shown above, then system is first getting the batch 00001111 of 12 Qty and will prompt for 2 qty of stock not available.
But ideally system should first get 00001111 of 12 Qty and then in the next line 00002222 of 2 Qty to meet the requirement.
Please let me know if this was clear and let me know if any possibilities to meet the requirement.
Thanks and Regards,
Gopinath Naik R

What are the User Exits for Sales Order creation process?

Hi,
what are the User Exits for Sales Order creation process? how can I find them?
thanks in advance,
will reward,
Mindaugas

Please check this info:
User Exits In Sales Document Processing
This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
Involved program components
System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
MV45ATZZ
For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
MV45AOZZ
For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
MV45AIZZ
For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
MV45AFZZ and MV45EFZ1
For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
User exits in the program MV45AFZZ
The user exits which you can use for modifications in sales document processing are listed below.
USEREXIT_DELETE_DOCUMENT
This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
USEREXIT_FIELD_MODIFICATION
This user exit can be used to modify the attributes of the screen fields.
To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
The usage of the field groups (modification group 1-4) is as follows:
Modification group 1: Automatic modification with transaction MFAW
Modification group 2: It contains 'LOO' for step loop fields
Modification group 3: For modifications which depend on check tables or on other fixed information
Modification group 4: is not used
The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
This FORM routine is called up by the module FELDAUSWAHL.
See the Screen Painter manual for further information on structuring the interface.
USEREXIT_MOVE_FIELD_TO_VBAK
Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBAP
Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBEP
Use this user exit to assign values to new fields at the level of the sales document schedule lines.
The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
USEREXIT_MOVE_FIELD_TO_VBKD
Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
USEREXIT_NUMBER_RANGE
Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
The user exit is called up in the FORM routine BELEG_SICHERN.
USEREXIT_PRICING_PREPARE_TKOMK
Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
USEREXIT_PRICING_PREPARE_TKOMP
Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
USEREXIT_READ_DOCUMENT
You use this user exit if further additional tables are to be read when importing TA01 or TA02.
The user exit is called up at the end of the FORM routine BELEG_LESEN.
USEREXIT_SAVE_DOCUMENT
Use this user exit to fill user-specific statistics update tables.
The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
Note
If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
User exits in the program MV45AFZA
USEREXIT_MOVE_FIELD_TO_KOMKD
Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMPD
Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
USEREXIT_MOVE_FIELD_TO_KOMKG
Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_MOVE_FIELD_TO_KOMPG
Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
USEREXIT_REFRESH_DOCUMENT
With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
User-Exits in program MV45AFZB
USEREXIT_CHECK_XVBAP_FOR_DELET
In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
USEREXIT_CHECK_XVBEP_FOR_DELET
In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
USEREXIT_CHECK_VBAK
This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
USEREXIT_CHECK_VBAP
This user exit can be used to carry out additional checks (e.g. for completion) at item level.
USEREXIT_CHECK_VBKD
The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
USEREXIT_CHECK_VBEP
This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
USEREXIT_CHECK_VBSN
You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
USEREXIT_FILL_VBAP_FROM_HVBAP
You can use this user exit to fill additional fields in the sub-item with data from the main item.
USEREXIT_MOVE_FIELD_TO_TVCOM_H
You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
USEREXIT_MOVE_FIELD_TO_TVCOM_I
You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
User-Exits for product allocation:
The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
USEREXIT_MOVE_FIELD_TO_COBL
Option to include new fields in structure COBL.
USEREXIT_COBL_RECEIVE_VBAK
Option to assign values from the document header to the new fields.
USEREXIT_COBL_RECEIVE_VBAP
Option to supply values from the item to the new fields.
USEREXIT_COBL_SEND_ITEM
A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
USEREXIT_COBL_SEND_HEADER
A changed field can be copied from the structure to the header (see source text MV45AFZB)
USEREXIT_SOURCE_DETERMINATION
You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
USEREXIT_MOVE_FIELD_TO_ME_REQ
With this user exit you can include additional fields for the following fields:
EBAN (purchase requisition)
EBKN (purchase requisition-account assignment)
USEREXIT_GET_FIELD_FROM_SDCOM
Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
USEREXIT_MOVE_WORKAREA_TO_SDWA
You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
User-Exits for first data transfer:
The following user exits can only be used for the first data transfer.
Note
Only use the user exits if the names/fields do NOT have the same name.
USEREXIT_MOVE_FIELD_TO_VBAKKOM
Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
USEREXIT_MOVE_FIELD_TO_VBAPKOM
Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
USEREXIT_MOVE_FIELD_TO_VBEPKOM
Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
USEREXIT_MOVE_FIELD_TO_VBSN
You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
USEREXIT_MOVE_FIELD_TO_KOMKH
You can use this user exit to include new fields for batch determination (document header).
USEREXIT_MOVE_FIELD_TO_KOMPH
You can use this user exit to include new fields for batch determination (document item).
USEREXIT_CUST_MATERIAL_READ
You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
USEREXIT_NEW_PRICING_VBAP
Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
USEREXIT_NEW_PRICING_VBKD
Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
User-Exits in Program MV45AFZD
USEREXIT_CONFIG_DATE_EXPLOSION
The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
User exits in the program FV45EFZ1
USEREXIT_CHANGE_SALES_ORDER
In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
User-Exits in Program RV45PFZA
USEREXIT_SET_STATUS_VBUK
In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
The following workareas are available for this user exit:
VBUK (header status)
FXVBUP (item status)
FXVBUV (Incompletion)
USEREXIT_SET_STATUS_VBUP
In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
The following workareas are available for this user exit:
FXVBAP (Item data)
FXVBAPF (Dynamic part of order item flow)
FXVBUV (Incompletion)
USEREXIT_STATUS_VBUK_INVOICE
You can use this user exit to influence billing status at header level.
User exits in the screens
Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
For field transports, you do not have to make changes or adjustments.
Example
A new field, VBAK-ZZKUN, should be included in table VBAK.
If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
User Exits in Program MV45AFZ4
USEREXIT_MOVE_FIELD_TO_KOMK
You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
USEREXIT_MOVE_FIELD_TO_KOMP
You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
EXIT_SAPFV45P_001
You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
Regards
Eswar

Batch determination at sales order level

Dear All,
We are using my sap erp ecc 6.0.We are using the batch determination at sales order level.We had a problem whenever customer requested deliver date is beyond the RLT date then all the old batches which are already assigned and dispatched with some other sales order,that old batches are becoming filled with 999,999,999....(infinity stock).And at the same time it is determining the batch for the sales order line item.
please help how to stop the old batches filling up with infinity stock.
regards,
Hari

please look into this and throw some light.
regards,
Hari

Problem in Printing of Sales order amount with program ZRD_RVADOR02

Hi,
We have one output type for printing the order aknowledgement for customer which is printing all details from sales orders for this we have made a program and form by copying the std. one Program : ZRD_RVADOR02 and form form : ZS1_RVORDER01_RD it is std. if we remove z we have done some little modification for header detail like company code and added ondition type etc.
for sales order basic price condition is PR20 and addiotnal price condition is PRXX in sales order the final price is addition of both but when both the price are same it is printing only single condition value and if both are different then it is priting addition of both means if PR20 and PRXX both are 5000 it is priting 5000 onlu actually it should print 10000 AND IF BOTH ARE DIFFRENT LIKE PR20 : 5000 and PRXX : 5000.01 then it is printing 10000.01 properly .
what can be the problem.
regards,
zafar

Hi,
Can u help on this issue.
regards,
zafar

Unwanted printing of advanced payment when printing a sales order or pick

It will be great to have an option of disabling the automatic printing of the advanced payment incoming payment when printing a sales order or invoice.
The option is currently not available on the document printing options.

No print sequence for sales order is setup.
But even before on 2007 version, it was SAP default to print always the incoming payment of an advanced payment on every sales order or invoice.

Picklist printing from Sales Order screen with Crystal Report

When attempting to print a Sales Order, we get a dialog box that allows us to choose either Sales Order or Picklist. Prior to moving to a Crystal Report based report, this dialog box would appear each and every time we tried to print the Sales Order. (Our process requires that we print the Sales Order to our Document Warehouse and then separately print the Picklist to a physical printer.) Now that we are using Cyrstal, the dialog box to select the form appears for the first print job, but when we try to print the other form, we no longer get the option to choose which form to print. The second attempt at printing then defaults to which form we printed first.
Under Print Preferences, it appears the box to "Print Picking Sheet" only applies to PLD. Other than closing out of the Sales Order Form and opening it back up again, is there a way to force SAP to allow me to choose which form to print each time I click Print?
And since we're on the topic, Is it possible to set up a print sequence to print the Sales Order to one printer and the Picklist to another one?

Are you on SBO 8.8 yet? If so which patch level?
There is a Print Sequence functionality built into this version (although we don't use it at our company at the moment). 8.8 will also allow you to attach Crystal Reports to any document (with a little work) and they will print just like a PLD document (albeit in a Crystal Viewer).
If you are not on 8.8 yet, how are you pulling up the Crystal Report for the the Sales Order? I'm guessing you are using some add-on to do this since the 2007 Crystal add-on didn't really handle document layouts very well.
I can expand on all of this if you want. But I'll need to know what version/patch level of SBO you are on. My company is on 8.8 PL15.
Brent

Collective Outputs for sales orders

hi,
Please can anybody help me to find out the outputs collectively for Sales Order.

Hi I asked a similiar question and this was the answer i received from PJ and it worked for me
Hi Paul,
SAP has provided a Standard Program,SD70AV1A for Mass printing of Sales Orders. Give the same to your ABAP team and ask them to assign a T-Code to this program.

Assign batch number from sale order to production order automatic

Dear all, I have a question for all. Please help me in this case
My scenario is make to order
I have a sale order, when i create sale order, i have assigned batch number at each line item.
When i run MRP for sale order (MD50), the system generate a planned order for it and I've converted to production order.
So when I view production order, I think that batch number what I've assigned to sale order will be assign to production order but that is not happen.
So, can you help me solve this problem. I think that sap can assign batch number from sale order to production order automatic but i don't know how to configure that
Thanks all

Hi,
To the best of my knowledge, when system is generating planned order / production order from sales order system doesnt copy batch number from sales order.
In fact , you are following wrong practice for generating batch no.
Follow procedure like this :
Create sales order without any batch assigning there. Run MRP with MD50 and then convert planned order to Production Order.
While creation / releasing of Production order, you have option to generate batch automatically by following way :
Go to OPKP (Production Scheduling Profile) -> Take your plant & give suitable name to Production scheduling profile-> Batch Management tab -
> Automatic Batch creation in the order maintain this field as
1 Automatic batch creation at order creation
or
2 Autom. batch creation at order release
This will generate batch number automatically at the time of creation or release of order.
Then follow same process i.e. Goods Issue, Confirmation & GR for production order.
So you will get sales order stock in the form of batch managed.
Check & revert if any issue in above flow.
Regards,
Tejas

Batch Printing for Sales Orders

Similar Messages

Maybe you are looking for