BA00 Output

Hello Everybody,
I need to trigger the ALE through output when a Sales Order is created. Can someone tell me how to do that? What are all the setting that I must take care of for that?
Thanks,
Sneha.

Hello Sneha,
Kindly check the following step :
1. Maintain the condition table for refering to the field catalog.
2. Maintain an Access sequence for the condition type.
3. Maintain Output condition type. Here make sure the value related to Processing routines as well as Partner function are defined.In the processing routine, put the name of the program related to ALE.
4. Assign Output type to Partner functions.
5. Maintain Output determination Procedure and assign it to output type.
These process are included in the output determination using condition technique for Sales Document.
Regards,
Sarthak

Similar Messages

BA00 output through mail

Hi All,
Please suggest .
Issue : For certain customers BA00 output is not getting mailed to their respective e mail Id's..
Observations : Here BA00 out put is not getting triggered using condition technique, it is getting proposed from Customer Master. There is no acees sequence maintained for BA00
I have checked affected customer master document tab for BA00 setting, it is in place.
Transmission medium is set to 5 i.e. external send, Dispatch time 4 i.e. immediate on save.
Not able to figure out as why it is not going through mail. Is there something I am missing in configuration?
Regards,
Nitin

Hi Yadav,
Thanks for your reply. I have done exactly as per your instructions. I could see the transmission request in SOST transaction but the status is 672 i.e. Waiting for communication service.
What does it mean ? How do I process it manually ?
Your help is really appreciated.
Regards,
Nitin Sawant

Text missing in BA00 output for languages FR and IT

Hello Friends,
We have configured the output type BA00 for the languages FR (French) and IT (Italian) and it is working fine.
But while taking the print out for the BA00 we found some characters like à, 'ê, are not printed on the print out.
Say for ex: générales
The above mentioned word was printing as g n rales, The characters lkie 'ê was missing.
In the same way for Italian language also.
So could you please help me in this regard.
REgards,
Ram.

Hello,
I share the same view as mentioned by J Prakash above.
But if you are able to see the FR & IT characters on screen properly & if they are not printed on Print-out properly, then you need to install some Driver Programs for your Printer.
Hope this helps,
Thanks,
Jignesh Mehta

Sales Order Acknowledgement BA00 output

Hi !
We would like the system to automatically set the output device on BA00 printouts to the default output device specified in the user profile (SU3 defaults).
Please let me know if there is a way to do this automatically (without requiring the user to pick their default output device again every time in VA02).
Thanks,
Anisha.

hi,
try using output determination for your requirement
menu path
img>sales and distribution>basic function>output control>output determination
maintain condition table
maintain condition types
maintainaccess sequence
maintain procedure
assign output determination to sales doc types
maintain condition record in vv11 click communication and maintain output device,number of copies,spool name
this will automatically trigged in sales order
hope this will help you
regards
senya

BA00 output type

hello.
with requirement 2, upon order confirmation output type BA00 can automatically be issued. is there a setting so that everytime an order is changed, BA00 is automatically re-issued?
thanks.

hi Jonathan,
Go to the output type configuration and check the 'Multiple Issuing' checkbox and this output will be issues everytime you save the order with changes.
thanks,
DB

BA00 Output Urgent

Hi all,
I created a new payment terms but the invoice output shows
the one thats in the order i.e. the correct one.
but the order output shows the diffrent payment terms the one that is not in the order or the customer master.
all partner functions are same.
Rgds

hi,
check your layout program with help of your abaper. It seems that part of text is either hardcoded or you would then need to check the print program whcih is fetching the values from VBKD table.
Your abaper can simply debug the output program and can fix it.
regards
sadhu kishore

Processing of Sales order output type BA00 processes another Z output type for acknowledgement.

Hi Friends,
I am facing below mentioned issue and request your suggestion to solve it
Via processing of sales order output type BA00 another Z output type is processed and acknowledgment is sent to SAP inbox( sost).
This is working incase of manual addition of BA00 output type and via standard program " sd70av1a", but this functionality is not working when i am calling this standard program in a Z report via batch job.
with the below code-
DATA: name TYPE tbtcjob-jobname.
         DATA: number TYPE tbtcjob-jobcount.
         DATA: print_parameters TYPE pri_params.
         name = 'ORDER_PRINTING'.
         CLEAR: range1.
*REFRESH: range.
         range1-sign = 'I'.
         range1-option = 'EQ'.
         range1-low = 'BA00'.
*        range1-high = 'ZBA1'.
         APPEND range1 TO range.
         CALL FUNCTION 'JOB_OPEN'
           EXPORTING
             jobname          = name
           IMPORTING
             jobcount         = number
           EXCEPTIONS
             cant_create_job = 1
             invalid_job_data = 2
             jobname_missing = 3
             OTHERS           = 4.
         IF sy-subrc = 0.
           SUBMIT sd70av1a WITH rg_kschl IN range
                           WITH rg_vbeln IN order_tab
                           TO SAP-SPOOL
                           SPOOL PARAMETERS print_parameters
                           WITHOUT SPOOL DYNPRO
                           VIA JOB name NUMBER number
                           AND RETURN.
           IF sy-subrc = 0.
             CALL FUNCTION 'JOB_CLOSE'
               EXPORTING
                 jobcount             = number
                 jobname              = name
                 strtimmed            = 'X'
               EXCEPTIONS
                 cant_start_immediate = 1
                 invalid_startdate    = 2
                 jobname_missing      = 3
                 job_close_failed     = 4
                 job_nosteps          = 5
                 job_notex            = 6
                 lock_failed          = 7
                 OTHERS               = 8.
             IF sy-subrc <> 0.
             ENDIF.
           ENDIF.
         ENDIF.
       ENDIF.
In this case only BA00 is getting processed but Z output type created for sending acknowledgment is not triggered.
Please suggest how can i achieve the required functionality.
Thanks,
Surya

Solved myself..
Thanks.
Br,
Surya

How to re-trigger BA00 after sales order has been rescheduled

Dear Gurus,
Could you please kindly advise how I could re-trigger BA00 after sales order has been rescheduled?
The scenario is following:
When the sales order was completed, the order confirmation output has been sent to the customer. But later, when the ATP confirmed quantity was changed or order was rescheduled, the committed delivery date has been changed. It caused confusion, because in the order confirmation letter we sent to customer, there is a different date.
I'd like to also trigger BA00 to resend the order confirmation, but I checked the output routine, it only checks if the order is completed or not. Shall I　ask ABAPer to add additional logic in the routine or there is other easier way to re-trigger BA00?
Many thanks in advance!

Have you allowed multiple issue for BA00 output type? In that case, you can manually trigger it from VA02. If you are trying to have it sent automatically, then add the logic into the routine.

Copy the standared output type to custome one

Hi,
i need to copy the BA00 output type to custome output type say ZB00. then it will appear my custom output type while we output a sale order. kindly give solution for this...

hi,
i done by following your steps.i can able to copied. then i have problem in output display while we using VA02 or VA03 to issue a sales order output. In that my customized output type has not been populate in that pop up window. so could you plz guide the steps what i have to do?

Sale order create BAPI and output types

Hi Experts,
In our organization, we are using BAPI BAPI_SALESORDER_CREATEFROMDAT2 to create sales order.
We are having no problem creating sales orders. But one more functionality they wanted to add.
We have a screen where user enters all the data and at the same time he selects weather the order should be printed or Faxed or both.
Please let me know where i can send this information in that BAPI and how.
I hope ORDER_KEYS is the table to send the data. If that is the case, could you please explain how that works and how that makes entry in NAST table.
Thanks,
ABAPer.

To propose output type automatically, you need to maintain proper output determination for the sales.
For example, you want to have BA00 output for every order, than you need to maintain the order type for that condition in VV11 transaction. Here you can maintain customer numbers. Now, when you create a Sales order for this customer and saves it, system automatically propose an output.
So, you need to maintain on output detemination to propose output.
Regards,
Naimesh Patel

IDOC_OUTPUT_ORDRSP - Multiple Issue Output

Hi All,
I have problem issuing multiple output for a Sales order Confirmation. BA00 is configured as:
1> I have assigned reqmnt 2 to the output BA00
2> Multiple Issue flag is checked
3> In Change Section, I have assigned FORM ZZ_ITEM_CHECK for program SAPMV45A. For now, I have code just as SY-SUBRC = 0. (Meaning for every SAVE of a order, trigger order conf output BA00)
4> WE20 is created without change flag (AENDE) selected/checked.
Steps:
1> Order is initially created and IDOC output BA00 is successfully triggered.
2> I go into the order second time, change something and hit SAVE. BA00 output is triggered but is with RED light. Error is
EDI: Partner profile outbound process code not available
Message no. E0 335
Diagnosis
An outbound partner profile could not be found with the following key:
/0003003919/KU/AG/V1/ZBA0/X/
I understand the program is trying to find WE20 with AENDE flag as Checked (hence 0003003919/KU/AG/V1/ZBA0/X/ ... "X" is is the AENDE flag in WE20 in Mesg control section where we input the process code and mesg type. This flag is not checked in my WE20.But the program is hoping to find it as checked.
If I "check/select" it in we20, initail order save conf o/p is not triggered as AENDE flag is not selected by the pgm and WE20 has it as checked. Either way it fails.
Any ideas?
Thanks
Bhaven

How many output type did you create ?
If you create two output type.
1) Outbound ORDRSP(BA00)-->Regular confirmation
First one trigger always once sales order is complete.
2) Outbound ORDRSP(ZBA0)->Normally they have this for change confirmation.
Second one will trigger only when there is changes in sales order.
I guess for first case you maintained in WE20(Partner profile).
and for second case(ZBA0) you didn't maintain partner profile. If you are not maintain, you have to maintain in WE20.
"Reward point if usefull".
Thanks,
Narayan

How to set up the output device in output determinatin with customer master

Hi,
I am doing the output determination using customer master and not conditions technique. Can anybody please let me know how to set up the output device . I have done the following:
1) assigned output determination procedure DB00001 to acct group 0001
2) added output type BA00 to customer master documents tab with print as the medium.
3) On creating a sales order and changing it its giving the message
BA00 515 No printer defined for output BA00
Please provide me with some suggestions , how to resolve this issue.
thanx
Jayant

1. tcode V/30 -> check BA00 type -> goto "print" tab -> what's set in the "print param." field?
2. IMG ->SD -> basic functions -> output control -> define print parameters -> V1 output -> for BA00 output type -> Assign a default printer. This is related with the "print param." set in step 1.
For example: if "print parame." is set to '1' in V/30, then the default printer is assigned to sales organization.
You can check F4 search help on the "print param." field (in V/30) to see what options you have.
If you want to specify printer by customer account, you may need to use userexit.
Edited by: Harry Wu on Jun 23, 2010 9:18 AM

Printing Street4 Street5 in SAPScript form BA00

Hello All,
I am trying to print additional lines of street address (i.e. Street4 and Street5) in the sales order confirmation SAPScript form (BA00) output. I see that the structure VBDKA is being used to display the Ship-to-party address details. However, it does not have the additional street fields in it.
How can I print these additional street lines?
Any help will be greatly appreciated.
Thanks,
Rugmani

In the INFO1 page of the SAPScript form I inserted the following code:
/:   IF &VBDKA-LAND1_WE& NE &SPACE&.
/*   * Ship-To Address (not identical to Sold-To)
/:   ADDRESS DELIVERY PARAGRAPH AS
/:     ADDRESSNUMBER &VBDKA-ADRNR&
/:   ENDADDRESS
/:   ELSE.
/*   * Output Partner (Sold-To)
/:   ADDRESS PARAGRAPH AS
/:     TITLE    &VBDKA-ANRED&
/:     NAME     &VBDKA-NAME1&, &VBDKA-NAME2&, &VBDKA-NAME3&, &VBDKA-NAME4&
/:     STREET   &VBDKA-STRAS&
/:     POBOX    &VBDKA-PFACH& CODE &VBDKA-PSTL2&
/:     CITY     &VBDKA-ORT01&, &VBDKA-ORT02&
/:     POSTCODE &VBDKA-PSTLZ&
/:     COUNTRY &VBDKA-LAND1&
/:     REGION   &VBDKA-REGIO&
/:     FROMCOUNTRY &VBDKA-SLAND&
/:   ENDADDRESS
/:   ENDIF.
However, I do not see the additional street lines filled in the form output.
Is there something wrong with my code? I think VBDKA structure does not accomodate the additional street lines. Is there any other structure that I can use? Do I have to change anything in the print program?
Thanks,
Rugmani

Delivery Output & Billing Output

Hi All,
Are there any standard transactions for Delivery and billing ouputs, other than VL02N & VF02
So that user can view and take print outs of only those documents.
Thanks & Rgds
Naveen

Hi Naveen
DELIVERY OUTPUT:
VL71    Output from Outbound Deliveries
VL74    Output from Handling Units
VL70    Output From Picking Lists
VL75    Shipping Notification Output
FOR GENERAL TRANSACTION CODE REFER BELOW:
VL02N    Change delivery document
VL04    Delivery due list
VKM5    List of deliveries
VL06G    List of outbound deliveries for goods issue
VL06P    List of outbound deliveries for picking
VL09    Cancel goods issue
VT02N    Change shipment
VT70    Output for shipments
BILLING:
VF02    Change billing document
VF11    Cancel Billing document
VF04    Billing due list
FBL5N    Display Customer invoices by line
FBL1N    Display Vendor invoices by line
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
VL04    Delivery due list. Run the delivery due with your order number to create the delivery
LT03    Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
In LT03 go to menu option Transfer Order -> Confirm Transfer Order
Enter
Save
The transfer order is now confirmed.
VL02N    Delivery change. EG: Edit the delivery to do the following Pack External customer material number = COO. External delivery number Waybill number. BOL Transport tag. Carrier Header partner SP (E.G. FXP). Tracking number = Packing Unit
FOR ALL THE REQUIREMENT:
Transactions
search_sap_menu - Finds the menu path to a transaction - Can either type in TX code in the search criteria or a description- ie. 1st try SE38 and then ABAP.... the returned result is 'bottom to top'.
EDI Specific Transactions
VOE1    Translation between EDI categories and SD item categories
VOE2    Table EDSC view. Customer link to sales area detail
VOE3    Table view EDPVW. Add partner types that will be transferred to the IDoc
VOE4    Table view EDPAR. Link external partner number with our internal number
WEDI    EDI Administrator Menu
BALE       Idoc Administration
Scheduling agreements
OVA9    Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.
OVAI    Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.
OVAJ    If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.
IDoc Transactions
WE09 / WE02    IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.
WE05    View IDocs
WE19    EDI test tool. Use to test inbound Function module changes.
WE20    Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing
WE30    Create IDoc extension type
WE31    Segment create
WE57    Assign function module to logical message and IDoc type
WE60    IDoc type documentation tool
WE82    Link Release detail to Extension IDoc Type
BD55    Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations
BD87    Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)
BALA    ALE Application Distribution
BALM    ALE Master Data Distribution
Output determination
856 - ASN
V/36   Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 V7ALLE SHAD for grouped ASNs. I.e. Group deliveries into shipments
VV21,VV22,VV23   Create output condition records for shipping. LAVA WE (Partner function) - We must add each new partner with VV21
VL71   Reissue output for deliveries
810 - Invoice
V/54   Maintain access sequence for billing documents
VV31,VV32,VV33   Create condition records for billing documents. (RD00 RE Billing party)
VF31   Reissue output for billing documents
855 Order Response
V/30   Sales document output types (BA00)
V/48, V/32, V/43   Maintain access sequence for sales documents
VV11,VV12,VV13   Create condition records for sales documents. (BA00 SP Sold to party)
Requirements coding
V/27    Create code to check requirements for output control. Used to check ZBA0 against BA00 output.
Sales & Distribution
Sales order / Quote / Sched Agreement / Contract
VA02    Sales order change
VA05    List of sales orders
VA22    Quotation change
VA32    Scheduling agreement change
VA42    Contract change
Billing
VF02    Change billing document
VF11    Cancel Billing document
VF04    Billing due list
FBL5N    Display Customer invoices by line
FBL1N    Display Vendor invoices by line
Delivery
VL02N    Change delivery document
VL04    Delivery due list
VKM5    List of deliveries
VL06G    List of outbound deliveries for goods issue
VL06P    List of outbound deliveries for picking
VL09    Cancel goods issue
VT02N    Change shipment
VT70    Output for shipments
General
VKM3, VKM4    List of sales documents
VKM1    List of blocked SD documents
VD52    Material Determination
Workflow
SWEAD    Event queue administration
SWE2    Event type linkages
SWE3    Event linkages
PPOME    Organizational Unit Maintenance
SWE5    Consistency Checks for Event Linkages
SWUD    Workflow Diagnostic Tool
General
The following section provides detail on other useful SAP areas.
Create delivery via transfer orders
Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.
VL04    Delivery due list. Run the delivery due with your order number to create the delivery
LT03    Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save
The Transfer order should now be saved. It now needs to be confirmed.
In LT03 go to menu option Transfer Order -> Confirm Transfer Order
Enter
Save
The transfer order is now confirmed.
VL02N    Delivery change. EG: Edit the delivery to do the following Pack External customer material number = COO. External delivery number Waybill number. BOL Transport tag. Carrier Header partner SP (E.G. FXP). Tracking number = Packing Unit
Purchase Orders
ME22N      PO Change
ME57         Create PO from purchase requisition
Goods Movement
MIGO    Post goods receipt
Other
MD04    Material Requirements. Shows material requirements and releases against materials
SE38    ABAP Editor. Used to modify ABAP programs
SM01    Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available
SHDB    Transaction recorder (BDC)
CMOD    User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work
SE16    Table contents display
SOST    View mails sent externally from SAP
SU53    Check authorization object
SQVI    Table Quickviewer Used to created quick client dependent reports
ST22    ABAP Dump Analysis
ST01    System trace
ST11   Display developer trace
ST05          SQL Trace
SM21          System log
ST22           Display short dumps
SM12          Display locked entries
Programs
List of ABAP Reports
Idoc
RBDAPP01   Post inbound Idocs to application documents
RBDAGAI2   Re-processing of IDocs after ALE input error
RBDAGAIE   Reprocessing of edited IDocs
RBDMANIN   Start error handling for non-posted Idocs
RSEINB00   Idoc inbound processing by file
RSEOUT00   Process outbound IDocs
General
RV80HGEN    Report 'RV80HGEN' for including customer-specific routines in the SAP standard source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition.
RSWUWFML    Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status' sent from SAP.
RHSOBJCH    Corrects the following error in workflow customizing:
Transport object PDST
Information Table SOBJ is consistent as regards key tables
**Error** Table HRP1600 Not an entry in table SOBJ
Information Table SOBJ is consistent as regards PAD tables
See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.
RSPO0075    Run report RSPO0075 to activate access method M for device types.
Reward if useful to u
Message was edited by:
        narendran vajravelu

Credit Block and Order Confirmation

I have a requirement where the client would like to send out some sort of an 'Order Acknowledgement' as soon as the order is saved if the order goes on Credit Hold. The system is set up to generate an order confirmation when there are no credit credit blocks. Standard SAP would not generate a BA00 output on save since the sales order is incomplete. Once the credit hold is removed and the order is saved the system will automatically generate that output (since the order will be complete) but till such time as the credit hold is not removed how can I generate an output to be sent to the customer just to indicate that their order has been received?
Suggestions would be greatly appreciated.
Thanks in advance.

Hi
Create a new Output Type (Copy of BA00) and assign the same in your Output Procedure in NACE Transaction. For this new Output Type do not maintain any requirement or maintain a new requirement (can be created in VOFM) as per your logic and assign the same for your new Output Type. You may also check the Requiremnt 9 and 11 if that is of your any use.
Regards
Amitesh Anand

BA00 Output

Similar Messages

Maybe you are looking for