Output - Billing - Configuration

Can someone help me in output configurations for Billing.
Kindly let me know the configuration settings.
Thanks.

Hi ,
OUTPUT DETERMINATION FOR BILLING DOCUMENTS:
For determining output at Billing document level, goto tranaction code NACE , and select the Application V3 , in the Menu bar there is a tab with OUTPUT TYPES,
Click on the OUTPUT TYPES and goto new entries and maintain the OUTPUT type with Z as prefix.
In the Output type assign ACCESS SEQUENCE ( which is nothing bt the combination to maintain the CONDITION RECORDS)
In the Output types, click on the PROCESSING ROUTINES where you have to assign the SMARTFORM & PRINT PROGRAM
SMARTFORM represent the Layout and the PRINT PROGRAM is used to code the logic and fetching the data from the table to SMARTFORM
SMARTFORM is created in the transaction code SMARTFORMS and the PRINT PROGRAM is written in the transaction code SE38.
Now Assign this output type to the OUTPUT DETERMINATION PROCEDURE
In the CONDITION RECORDS maintain the condition records with the combination given in the Access sequence.
Now while creating the Billing document check the Output assigned or not, it will assign automatically and will be in the Yellow status
Now using the Program RSNAST00 this will be processed and sent to printer.
If you want to process the output automatically you have to schedule the Job for the Program RSNAST00
please also check the below link
[OUTPUT DETERMINATION FOR BILLING|http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBFOC/SDBFOC.pdf]
regards,
santosh

Similar Messages

"change output" feature in output type configuration

Hi
I am trying to find a way of automatically triggering repeat output on change of delivery date in order.
   In output type configuration-general data there is a are for change output the F1 helps reada like this "..........The routine in the program checks which changes should result in a changed output being sent. ......"
   If anybody has worked on this functionality, please help me by giving any relevant input.
TIA

Take a copy of output requirement 014 and change the code to make it work for your delivery date. Output requirement 014 is provided in standard SAP for BV - cash sales. In cash sales, if the net value is changed, the output is automatically retriggered.
Remember the KOMKBV1 in the below code represents the sales orders communication structure. If you are doing this requirement for delivery document use KOMKBV2 and for billing document output determination use KOMKBV3.
***INCLUDE LV61B014 .
      FORM KOBED_014                                                *
Requirement to create an new order confirmation / invoice when     *
the net value is changed.                                          *
FORM KOBED_014.
SY-SUBRC = 4.
If the net value has changed, resend the Output type RD03
IF KOMKBV1-NETWR NE *KOMKBV1-NETWR OR
     *KOMKBV1-NETWR IS INITIAL.
    SY-SUBRC = 0.
ENDIF.
ENDFORM.
      FORM KOBEV_014                                                *
      Reference to KOBED_014                                        *
FORM KOBEV_014.
   PERFORM KOBED_014.
ENDFORM.
Thanks
Kapil Sharma

How to repeat output billing documents

Hi Guru;
How to repeat output billing documents ; because after VF04 maintain billing due list,
all intercompany billing doucments can not be printed throught our local printer. We are using Biling type as intercompany billing and output as print.
Regards,
Raj

Hi Raj,
Please use T-Code VF31,output from Billing
under Message Data select the output type that you need, enter the transmission medium as print and select processing mode as Repeat processing.
And in billing data mention the correct billing document for which you want repeat output.
Hope Above will resolve your problem for Repeat output for Billing Documents.
Regards,
Sandeep

GR,GI and Transfer Posting Output Determination configuration settings

Hi All,
Please explain the output determination configuration settings for GR,GI and TR.
Thanks in advance.
regards
sapmm

Please check this link out for details:
Output dertermination for GR/GI
Output type configuration for GR : MB90
Edited by: Afshad Irani on Apr 19, 2010 3:24 PM

Production Order : OUTPUT Type Configuration for Production Order as EDI

Dear SDN All ,
OUTPUT Type Configuration for Production Order.
Doubt in third Point
We have found the IDoc " LOIPRO01 " for Production Order
(Please confirm that this IDoc can be used for outbound IDoc for Production Order)
And foloowing
1. Defining the Output Type for Particular Application.
 T-Code: NACE
A. Output type have created upder application "ME" description : "Inventory Management"
B. " ZEDI " created for getting output as EDI type
 ZEDI is copied from "WF01" output type. and
 Transmision mediam as "EDI"
 Program : RSNASTED
 Form Routine : EDI_PROCESSING
 (Please confirm is this for IDoc creation)
2. Partner profile creation:
A. Partner profile created under logical system and
B. and In outbound parameter declared as "LOIPRO"(This is for sending the IDoc "LOIPRO01" to XI system).
3. Customization for output type for Proction Order -- (For CO02,CO08) ---
 A. But only one functional customization is remaining to do, for getting the IDoc while saving the Production Order in T-Code "CO02" and "CO08"
 For Example:
 in sales order transaction va02 (in DBI 450 client) and select any Sales order.
 & select following menu path.
 Extras --- > Output -
> Header -
> output
 Here we can set our output type "that U defined in NACE Transaction-Code"
 Like the same way I want to set output type for CO02, CO08 transaction.
But I couldn't find the menu Item in Co02 and Co08 for setting the output.(like VA03)
Please help me out for setting the output type for Production Order Creation.
Thanks in advance,
Dhanabal T
Message was edited by: Dhanabal T

Hello.
I have a similar requirement. Did you guys find the solution?

Output type configuration set up

Hello MM Masters
I have to create Material Master, PO, delivery, Goods receipt inbound, inventory adjustments in SAP. I am developing some interfaces to send these to external distribution vendor. I am using Idoc message type matmas, orders, desadv, mbgmcr01, shpcon (WHSCON). Can anyone help me to find the right Application, output types, procedures used for setting up output type configuration in SAP to generate idocs from these transactions during change/create
Thanks
Ricky

Hello Ricky,
For triggering Idoc you will use your regular output type but medium will be "Send Message via EDI / ALE"
More information you will find with the following link<a href="http://help.sap.com/saphelp_46c/helpdata/en/15/3cf334c20ccc52e10000009b38f83b/frameset.htm">IDoc interface</a>
Hope this helps.
Regards
Arif Mansuri

Output Determination Configuration Setting for GoodsIssue(Transfer Posting)

Hello Gurus,
Can any one give the details for Output Determination Configuration Setting for Goods Issue(Transfer Posting).
Thanks N Regards,
Venu MG

hi,
PRINT OUT OF MATERIAL DOCUMENT AT GI/Transfer posting:
1. Maintain the Printer Name in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Printer Setting
2. Ensured in SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Item Print Indicator, 1 stands for Matl Doc print out
3. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Gen Settings->Print Version, maintain Print Version 2
4. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Print Control->Maintain Print Indicator for GI/Transfer Posting Documents
5. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Maintain Output Types, for the Output types WE01, WE02 and WE03, ensure the foll:
a. Default Values: Dispatch Time is 3 or 4 as per reqmt. and Tr medium is 1
b. Print Parameter is 7
6. In SPRO->Matl Mgmt->Inv Mgmt and Phy Inv->Output Determination->Printer Det->Pr Det by Pl/StoLoc, maintain the Output device for all your Plants
7. In MN21, for Tr Type WE, Print Version 3, maintain Print Item as 1.(Condition records)
8. While doing MIGO, ensured that in General Tab, you get "3 Collective Slip" beside the Print Indicator and you tick mark the field.
Now go to MB90 entered the output type as WE01, Tr m as 1, Sort or. 01, Pro.mode as 01, and executed. Sytem outputted all the material documents that has to be taken print out.
Regards
Priyanka.P

Output determination configuration

Hi Expert,
Please give me the all steps for Output determination configuration for SHIPMENT (txn VTO2N).
Since I am technical guy I am not aware with this configuration, so please consider it and please provide me from scratch.
As I create one output type ZAV7 it is similar to ZA02 existing one.
i copied existing program that is running for ZA02.
AND ASSIGNED THIS COPIED PROGRAM TO NEW FORM i.e. ZAV7(output type).
After that I transfer it to 220 client.
when I run Txn VT02N. for ZA02 the form is coming properly.....but for ZAV7.....
it gives the message
You have specified an output category which has not been defined according to the output determination procedure.
After this message i am not able to do the configuration.
thanks
Babbal

Hi Babbal,
You have to assign ouput type to the ZAV7.
Please follow the following configuration:
Go to SPRO> Logistics execution> Transportation> Basic transportation functions> Output control> Maintain output determination for shipments
Steps-
1. Maintain condition table or u can use the existing table 017 "Shipment type" or 022 "transport planning point and shipment type".
2. Maintain access sequence: Here you can use standard access sequence 0001 or 0002 based on the condition table you have maintained.
3. Maintain output type- Add new entry ZAV7, give description. In general data tab page assign the access sequence you used. Check the access to conditions. For default values tab page- maintain the dispatch time as 4 Send immediately, transmission medium as 1print output, partner function as CR. in storage system tab page maintain the storage mode as 1Print only. In Print tab page maintain the parameter as 8Transportation planning point.
Double click on Processing routines and maintain the program, form entry and form name program.
Double click on Partner function and maintain medium as 1Print output and functional partner as CR. Save it.
4. Maintain output determination procedure: Standard procedure will be already maintained V70001 "Transportation Output". Select the procedure and double click on control data. Click on new entries and maintain the step as 30, counter 1 and enter the output type ZAV7. Save this.
5. Assign output determination procedures: maintain the shipment type, the output determination procedure and output type. Save this.
Please reply for any further clarification.
Regards
Suvankar

ISU Billing Configuration and Billing Cycle

Hi All,
Can anyone please provide me billing configuration and cycle in ISU information?
Thanks,
Shahid
Moderator note: Please read the Research Resources and Rules of Engagement and other sticky posts for rules and hints for research.
Edited by: William Eastman on Mar 9, 2010 7:19 PM

Hi,
You can define document type & no. range for reversal document type in following path:
No . range
Utilities Industry/Invoicing/Invoice Processing/Define Number Ranges for Print Documents
Document Type:
Utilities Industry/Invoicing/Invoice Processing/Define Document Types for Print Documents
then allocate document types to print document:
Utilities Industry/Invoicing/Invoice Processing/Allocate Document Types to Print Documents
In this define creation reason, company code & document type
Hope this may help you.
Thanks,
Harshal

Output determination configuration for SHIPMENT (txn VTO2N)

Hi Expert,
Please give me the all steps for Output determination configuration for SHIPMENT (txn VTO2N).
Since I am technical guy I am not aware with this configuration, so please consider it and please provide me from scratch.
As I create one output type ZAV7 it is similar to ZA02 existing one.
i copied existing program that is running for ZA02.
AND ASSIGNED THIS COPIED PROGRAM TO NEW FORM i.e. ZAV7(output type).
After that I transfer it to 220 client.
when I run Txn VT02N. for ZA02 the form is coming properly.....but for ZAV7.....
it gives the message
You have specified an output category which has not been defined according to the output determination procedure.
After this message i am not able to do the configuration.
thanks
Babbal

Hi Babbal,
You have to assign ouput type to the ZAV7.
Please follow the following configuration:
Go to SPRO> Logistics execution> Transportation> Basic transportation functions> Output control> Maintain output determination for shipments
Steps-
1. Maintain condition table or u can use the existing table 017 "Shipment type" or 022 "transport planning point and shipment type".
2. Maintain access sequence: Here you can use standard access sequence 0001 or 0002 based on the condition table you have maintained.
3. Maintain output type- Add new entry ZAV7, give description. In general data tab page assign the access sequence you used. Check the access to conditions. For default values tab page- maintain the dispatch time as 4 Send immediately, transmission medium as 1print output, partner function as CR. in storage system tab page maintain the storage mode as 1Print only. In Print tab page maintain the parameter as 8Transportation planning point.
Double click on Processing routines and maintain the program, form entry and form name program.
Double click on Partner function and maintain medium as 1Print output and functional partner as CR. Save it.
4. Maintain output determination procedure: Standard procedure will be already maintained V70001 "Transportation Output". Select the procedure and double click on control data. Click on new entries and maintain the step as 30, counter 1 and enter the output type ZAV7. Save this.
5. Assign output determination procedures: maintain the shipment type, the output determination procedure and output type. Save this.
Please reply for any further clarification.
Regards
Suvankar

ISU Billing configuration

Hi Expert,
Please let me know what are ISU Billing configuration setting has to done in system and pls provide the document on same.
Is there any config setting related ot Interim billing & Reversal document number range and document type.
Thanks in advance

Hi,
You can define document type & no. range for reversal document type in following path:
No . range
Utilities Industry/Invoicing/Invoice Processing/Define Number Ranges for Print Documents
Document Type:
Utilities Industry/Invoicing/Invoice Processing/Define Document Types for Print Documents
then allocate document types to print document:
Utilities Industry/Invoicing/Invoice Processing/Allocate Document Types to Print Documents
In this define creation reason, company code & document type
Hope this may help you.
Thanks,
Harshal

Output type configuration in nace

Hi Experts,
I have a requirement in invoice smartform, so i want to create my own output type .Actually that is normally done by functional.
But i need to know how to configure zoutput type in nace.
some steps i followed.in NACE>V3(billing)>new output type(ZINV)>i added new one.
ofter that in VF02 i want to message means communication method it shows the error that "ZINV" is not defined.
i though i missed some steps , so please can u give the total procedure how to configure in NACE and how to add in VF02.
waiting for valuable replies.
thanks.

Steps would be:
1. Create output type for application either copy / new - and assign program and form name
2. assign the created output type in existing / new procedure (output type procedure)
3. if it is a new procedure then that also need to assign to a correct sales document type ; in this case it has to be assigned to billing type...transaction V/25
Configuration path:
SPRO -> Sales and distribution -> basic functions -. output control -> output determination -> determination technique -> Maintain Output Determination for Billing Documents
Thanks

Output type configuration

Hi,
I have one doubt. What is the difference between configuring the output type through nace and spro. For few transactions, i see that the functional team add the custom driver program or the form name through NACE and for some cases through SPRO. Can you tell me the difference?
Thanks.

For purchase, Inventory & sales (Sales, Delivery & Billing) related transactions, we have to configure the output types through NACE.
For PP, QM & FI related transactions we'll go with SPRO or specific transactions like, OPK8, FBZP etc..

Output type configured as "CanNotChanged" (NACE) and process mode 2 in VF31

When we configure a billing document output type as "CanNotChanged"
(NACE), we can no longer use the processing mode 2 in the VF31
transaction to repeat the printing of the documents which have been
printed allready once.

Acording to SAP, this is the standard behaviour of the software

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

Output - Billing - Configuration

Similar Messages

Maybe you are looking for