Packing at delivery note & billing

Let me put my req:
I have created delivery, ( am using Packing process in delivery)
I have done packing ,its working fine.
When I take the output ( output type:LD00- delivery note) , main item & sub item ( packing item ) also appearing in delivery note.
am not sure, is it right practice to print packing item in delivery note?
( all this packing items can be printed on PL00- Packing list including Handling Unit Numbers)
I have created a sales order- vth FERT material .
created delivery wrt sales order-
When you select line item in delivery n click in Edit-pack, system will prompt with the screen which appears in upper section is for packing items & lower section is for fert materials.
Here we need to choose fert material & enter the qtty in "partialy qtty" filed (expected no.of units to be packed in packing material" & click on "per partial qtty" , so that system search for suitable packing material. then all the fert material will be packed into packing materials.
Once we clik on"F3/back" icon, we will observe that packing material will be displayed as subitem & fert will be in main item.
in picking tab:- we pick both the line items n press "PGI".
now delivery will be saved. To create billing VF01 - enter delivery doc no,
at the stage, system actually shouldnt copy the subitem(packing items ) into billing, where as in my case,system is copying packing items into billing.
I have nt changed either copy control from LF-F2 or TAL std settings in IMG.
Still system copying packing items into billing.
any inputs???

Hi again,
According to SAP documentation, clearly the TAL returnable packaging item should not being invoiced, as it is invoiced later with the Returnable Packaging Issue if the customer does not return the packaging item.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/dd/560051545a11d1a7020000e829fd11/content.htm
You seem to have the right customizing so maybe it is a mistake in standard SAP, because the system should not even try to invoice this item as it is not relevant for invoicing.
In a first step, I would go into copy control configuration between delivery and invoice and mark the item category TAL as "don't copy". This way it will not get copied into the invoice.
In a second step I would invoice the rest of the delivery and afterwards check that the delivery document is "closed" from a document flow point of view (check the SD document flow). If it is the case, then I would close the problem.
Best Regards,
Franck

Similar Messages

SAP standard Report-PO, delivery Note, Bill of lading,Header txt,GR/GI slip

Dear Firends,
Kindly tell me the SAP standard Report which give the details of
Po number, delivery Note, Bill of lading, Header text and GR/GI slip no.
Thanks in advance.
Regards,
william

Hi,
You can get all these fields in MB51 report by selecting the relavant fields in the selection variant. If any of the required fields are not available than you can add those in img -going tothe Inv Mgt-Reporting - Define field selection for material document list.
Dhruba

Double Invoice Check - Against the Delivery Note/ Bill #

Dear All,
I have a requirement here, Bit different from the Regular Double Invoice Check,
I will receive the Material A, 10 different times, will do the GR 10 times & enter the Bill # & Challan # during GR. While posting the Invoice i want the system to check against which Bill # i am posting the invoice. Say during GR my Bill #s were 1 to 10. I receive the Invoice from my Vendor from 1 to 5 today, so i posted the invoice. After few days He will send a duplicate Invoice with Bill # as 5, & he will inform me that he lost original Invoice so he is sending the duplicate. As i have'nt posted Bill # 6 to 10, system will accept the Bill 5 also again. How can i avoid these things ?
regds,
CB

Hi,
Already I am maintaining these Bill # & Delivery Challan # during GR. My issue is during Invoice i want a check. In Invoice we have a reference field at header, If i am posting a single GR as a single invoice thats OK. But if I am posting more than 1 GR in single Invoice, where can i maintain the Bill # ? Any solutions pls ?
regds,
CB

Regarding- Packing Line Item Not Displayed in the Delivery Document.

Hi,
I have 2 queries
1) Have created separate Material Type Packaging for my packing material and the item category group used is VERP, my Orginal Material is getting packed in the Delivery Document, however the packed item is not coming as a separate line item in the Delivery document, I have maintained the item category settings for the Delivery Packing Material and also the packing Material contains stock,
2) The Plant and Storage Location for my handling unit need to get defaulted autmatically in the delivery document what settings should I configure for the same.
Kind Regards
Atul Keshav

Hi,
Find the below threads, which is explained in context with returnable packaging, same will be useful for you.
[Re: returnable packaging]
[Returnable packaging process;
Regards,
Reazuddin MD

Billing note and delivery notes

Hi, please tell me the what is meant by billing note and delivery note

Hi Madhu,
Delivery Note:-
Its a Document which consists of all details realated to the Delivery Like,
Customer,Material, Quantity, Price Etc., which is complusory document while leaving the Goods from the Plant and have to submit the Delviry note to the geat men.
Billing Note:- It is also a document which consists of detials like customer,material,Quantity and price et., which is also compulsory doc while the goods in the Trasnsit.it will be use for sales tax,excise etc.,
Hope this clarifies your doubts,Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Goods receipt of packed inbound delivery is not allowed

Dear all,
I have a scenario that as per of business process,i have to post Packed inbound delivery in MIGO .
But i am getting an error says inbound delivery cannot be packed during posting in MIGO. I know that i can post it through VL32N without any problem. Since i need to capture damage,short or excess and some reference numbers and date of production and expiry for the items i need to post through MIGO option instead of VL32N.
I have already checked in our client IDS ,it is allowing to pack without any errors but in Development server i am getting this error.
I changed the item category control ELP of inbound delivery also but of no use .
Any hindsights on this both funtionally or tecnically will be of great help.
Thanks and regards,
Jothiswaran.
Edited by: A. Jothiswaran . on Nov 12, 2009 8:32 PM

Hello,
To my knowledge packing through MIGO is not possible.
If your SLOC is HU managed and you have done the configuration of u201Cdefault value of delivery and HU requirementu201D
SPROLGHandling Unit ManagementBasicMaterial managementInventory managementsecond option, then your issue will be solved.
In this case, when you post the MIGO with all information you will get IBD delivery number and not material document number. After that you can pack the material in IBD
Thanks
Milind

Field FKSTA- Billing status of delivery-related billing documents not getting updated

Hi Experts,
I have a requirement wherein I need to fetch the FKSTA - Billing status of delivery-related billing documents into the datasource 2lis_11_VASTI. I have checked a lot of threads on this topic but have not found a concrete solution yet.
I have checked the settings in vov7 and vov8 and everything seems to be in place. I have also checked in table VBUP, when I filter based on field FKSTA = 'C', it shows me the outbound delivery document nos. But when I use the related sales document, it shows me blank values. VBUK as well doesn't show any values for field FKSTK.
I would like to know how and where I can identify the 'billing status of delivery- related' document.
I can see in VBUP table that if I enter the sales document no. related to the delivery document, it does not show the correct status. I believe that the statuses should ideally get updated to the underlying VBUK and VBUP tables. Is there any way to update and align them?
Is there a workaround, a similar field that i can use for datasource enhancement that will give me the correct values?
Appreciate any help I can get on this as it is urgent.
Thanks,
AM

Hi,
You are correct that stauts is updated in table VBUK and VBUP.
However, a sales order does not determine a billing status for delivery related billing, field
VBUP-FKSTA is only determined for delivey.
So, it is correct behavior that VBUP-FKSTA = BLANK when searching VBUP with
VBUP-VBELN = sales order number.
Just because of above reason, you will not find billing status field in VA03 -> goto header/item;
you could only find billing status field for delivery in VL03N -> status overview.
It seems that you are trying to find out sales orders that have been fully deliveried and fully billed, am I right? As far as I know, there is no directly table/field/tcode that could meet your requirement.
You could consider following workaround:
firstly, get a list of deliveries that have been fully billied(search VBUP with VBUP-FKSTA = C or search VBUK with VBUK-FKSTK = C);
Secondly, using these deliveries to search table VBFA to find out related sales orders.
Hope this helps.
Best regards,
Crystal

MIGO_GR fill delivery note field from manual entry in bill of lading

I have to fill header field delivery note from manual entry in bill of lading in tcode MIGO_GR for mopvement type 101.
I searched for the exits and BADI's but header fields are not in changing parameters.
Has anybody worked on automatically filling the delivery note field in MIGO_GR transaction from bill of lading field or a value from database?

Hi You can use MB_MIGO_BADI Badi.
Thanks,
Anmol.

Customer invoice n delivery note print together at time of Billing

Hi,
Customer want invoice and delivery note attach together.
once billing document saved invoice and delivery note print together immediately.
plse suggest
Thanks in advance..

HI
In the Out put determination maintain Those 2 Output Types and assign to the Billing Type
At the time of maintaining the Condition record through VV31 , maintain the Dispatch time " 4" and message Transaction Medium "1"
After that select the Line and Click on Communication Give Output Device and Tick " Print Immediately Field
Regards,
Prasanna

Bill of Lading and Delivery Note

Hello Expert,
Please let me know the the difference between Delivery Note and Bill of Lading.
Also, provide me the respective message type to be used in interfacing technique.
If you can take an end-to-end example which can describe both, will be great help.
Regards,
Sonal

Sonal,
Let me first tell u the defn of both in simple words :
Bill of lading or BOL : It is one of the transportation documents in shipping.
Example : Say your company wants to send some goods from Mumbai to Pune. and your shipping partner for this is say DTDC. Now in this case the shipper will issue Bill of lading to the delievring org i.e your company after veryfying the goods. Now your company has to send the BOL to the customer. In turn customer will produce this BOL to shipper to claim the goods . This is like a Waybill or say token or pass in simple word.
In SAP, BOL is enabled by means of some standard output types like CMR1, CMR2, BOL1 etc.
we can also capture EDI output types like ALTR which can be used to transmit the BOL to other systems.
Delievry Note: It is basically the output type generated during the delivery creation. It can be used to provide the details of goods sent during the delivery creation.
again if we will carry same example Its just like information,send to customer that,we have delivered material to you..
Hope it will help.
Thanks,
Raja

Delivery Note/Pack List

Can somebody post, or send me, the print program for the SmartForm Delivery note/Pack List (output type LD00)?
Regards,
Davis

Ferry, the code that you sent me doesn't seem to be complete; it is missing three includes. Does anybody have the following includes that they can post or send me? The report is RDE_DELNOTE.
REPORT RLE_DELNOTE.
declaration of data
INCLUDE RLE_DELNOTE_DATA_DECLARE.
definition of forms
INCLUDE RLE_DELNOTE_FORMS.
INCLUDE RLE_PRINT_FORMS.
Regards,
Davis

Delivery once billed should not allow again for billing

HI Friends,
Delivery once Billed should not allowed for billing again.
how to solve this, give the user exit if possible
Thanks & Regards
T.A.V

Hi,
Please ensure that the Copying Requirement routine 003 is assigned at the header for your billing and delivery type in transaction VTFL. Also set up 004 at the item level. I hope this will resolve the issue.
Regards,
Murali

Text is not copying from delivery to billing

Dear All,
I have determined the text from delivery to billing corretly.
but it is not copied from delivery to billing.
Is there any settings in copy control kindly suggest.
Best regards,
ramesh

Use T.Code VOTXN"
Choose on Billing document - Header.
Click on Change button.
Select your text procedure.
You can know your procedure by clicking on the tab Text procedure assignment.
Click on Text ID's in Textprocedure.
Select your text id.Check the tick mark under "Refer/Duplicate" field.
And also check your access seqence
For understanding/reference, kindly refer following SDN thread
- Text Determination Procedure from Sales order to Delivery ,&Billing
- Re: Copying Text from Sales to Sales Document
Thanks & Regards
JP

Selective line item to be printed in Delivery Note

Hi All!
There is a specific requirement that the packing material used should not be printed but the number of packed units should get printed with the identification number.
for e.g. There is 100kg of Aluminium strips [Material XYZ] which is to packed by reels [Material ABC]. Suppose we use 2 reels to pack the 100kg strips. Then in the Delivery note it should print only :
Material XYZ 2reels 100kgs
The packing material has no billing relevance in our scenario, hence it is not to be shown.
By removing the indicator for billing relevance and pricing in Item Catergory HUPM, I am getting the pricing as zero but the line item created due to packing is getting printed.
Please suggest how to solve this.
Thanks & regards
Karthik

no replies.

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

Packing at delivery note & billing

Similar Messages

Maybe you are looking for