SO delivery date on A/R invoice

Dear All,
Our customer would like to have SO delivery date on the A/R invoice layout. So I create UDF and FMS for A/R invoice. Then I will be able to have SO delivery date for each line when they use 'copy to'.
The problem is, they have some text lines on the A/R invoice. When i copy SO to A/R invoice, the system will pop-up a window to ask, if we would like to change the format of the line. How many text lines we how, we will have how many pop-up window. We have to say 'no' for that window. Otherwise, SAP will not copy text to A/R invoice.
How can I get rid of that pop-up window? Thanks a lot.
Regards,
Yuka

Hi Yuka,
Why are you using FMS in UDF for Base Document Date(SO or Delivery Date) on A/R Invoice Rows?
In SAP B1 behaviour, Base Document No. & Date default in Target Docuement Rows.
Try this, you will be get the SO (or) Delivery No. & Date in A/R Invoice Document Print.
->> Open the A/R Invoice PLD.
->> Create 2 Database Fields in Repetetive Area and Assign the Base Document No. & Date fields.
Base Document No. (SO. or Delivery No.)
Table -> INV1 - A/R Invoice - Rows.
Column -> BaseRef - Base Document No.
Base Document No. (SO. or Delivery Date)
Table -> INV1 - A/R Invoice - Rows.
Column -> DocDate - Posting Date.
Regards,
Madhan.

Similar Messages

GR/Delivery Date required in the Invoice Verification screenlayout

Dear Forum,
We notice that when the users perform the Invoice Verification thru MIRO, in the screenlayout corresponding to 'All Information' the system populates the date under the 'Delivery Date' column, however, this date corresponds to the Delivery Date mentioned in the PO Header and does not reflect the actual GR Date. The users want this to be replaced by the actual Delivery Date when the goods were received and GR was posted. Is there a way to replace this or else modify the layout so that the actual Delivery Date is populated. The reason is that the users want the baseline date to be replaced by the actual GR date and do want to go for another step involving the scrutinizing of the PO History.
Thanks for the help!
Regards

Hi Venkat,
Thanks for the help, is there a way to change the layout of the MIRO screen such that we can view the actual GR or the Delivery Date while doing MIRO.
Regards

Outbound delivery date in June and customer invoice post in July,tax rate?

Hi Experts
tax rate (June)=22%
tax rate (july)=24%
issue is Outbound delivery date in June and customer invoice post in July,so sytem taking tax rate =24% instead of 22%.Because outbound delivery is happened in June.
Please let me know that,
1)how system picking tax rate on base like billing date or service render date or ...?
2)how to take tax rate (june)=22% in July posting.
regards
sachin

Tax Rate is picked based on the pricing date.
You need to check with your SD collegue to configure the pricing date to be equal to outbound delivery date to pick the outbound delivery date based tax rates.
Regards,
Gaurav

AR Invoice date should not be less than delivery date

How can i make an alert for user when they will prepare AR Invoice?
Example:
If Delivery date is 01-10-2010 and Invoice date should be later or same but not less than delivery date(01-10-2010).
if Invoice date is less than delivery date then This data should not be added into the database.
So there is any way to stop this error.
Thanks
Mizan

Dear Bala,
Here is the SP:
set ANSI_NULLS ON
set QUOTED_IDENTIFIER ON
go
ALTER proc [dbo].[SBO_SP_PostTransactionNotice]
@object_type nvarchar(20),                     -- SBO Object Type
@transaction_type nchar(1),               -- [A]dd, <u>pdate, [D]elete, [C]ancel, C[L]ose
@num_of_cols_in_key int,
@list_of_key_cols_tab_del nvarchar(255),
@list_of_cols_val_tab_del nvarchar(255)
AS
begin
-- Return values
declare @error int                    -- Result (0 for no error)
declare @error_message nvarchar (200)           -- Error string to be displayed
select @error = 0
select @error_message = N'Ok'
--     ADD     YOUR     CODE     HERE
If @object_type='13' and @transaction_type='A'
BEGIN
If Exists (Select distinct 'error' from [dbo].[OINV] T0 Inner Join INV1 T1
On T0.DocEntry=T1.DocEntry Inner Join DLN1 T2 On T1.BaseEntry=T2.DocEntry
Where T0.DocDate<T2.DocDate
And T0.DocEntry = @list_of_cols_val_tab_del)
BEGIN
Select @error = -1,
@error_message = 'DocDate for Invoice Should not be Less than Del. Date. So You can not Add this Doc'
End
End
-- Select the return values
select @error,@error_message
end
Regards,
Mizan

Invoice Date Based on POD Date and Requested Delivery Date

Hello Experts,
Could you please Help me How to get the Billing date in the invoice document based on POD date if the POD Report has been Posted , If not the system should pick up the requested delivery date.
Thanks for your time

Hi,
Create an copy control routine (T.Code VOFM) as assign in copy control setting between Delivery doc to billing docuement (T.code VTFL).
The new routine will be created with copy of existing routine assign under "Copying requirements" at item level, and assign on same place.
Pl take help of ABAPer to write the new routine.
regards
Vivek.
Edited by: Vievk Vardhan on Jan 7, 2010 1:50 PM

If free upgrade is available to those who purchase after 6 June 11, Purchase should mean the order date or the invoice date or the delivery date?

If free upgrade is available to those who purchase after 6 June 11, Purchase should mean the order date or the invoice date or the delivery date?

Apple usually has gone by the invoice date, which is the date Apple usually considers to be the "purchase date" for warranty and other programs, but precise details for the Mac OS X 10.7 Up-To-Date program have not yet been released, so that may differ. We'll have to wait until they open the program to know for sure.
Regards.

Change delivery date on sales order -- change of Billing date on item

Hi,
We are trying to change a delivery date for a sales order's item, if we do so normally the billing date on that item's billing tab will change automatically also.
Now, for a specific sales order the billing date in the billing tab is not changing.
We compared 2 sales orders .. the same statusses - no blocks - ... and with one it works (changing of the billing date) and with the other it does not work..
Please help !
thanks a lot!

Hi,
Check the following.
If invoice dates are defined for the customer, the system proposes the billing date from the invoice date calendar. If no invoice dates are agreed, then the actual goods issue date is formed on the basis of delivery related billing. In order related billing, the billing date of the order forms the basis of the billing date.
If you are billing services, the system proposes the date of services rendered. You can change the date manually in the sales document.
If you are using a billing plan to bill a project, the system can propose billing dates for the billing plan on the basis of planned or actual dates in the corresponding milestone.
In a billing plan for a maintenance or rental contract, you can specify rules by which the system determines billing dates on the basis of other dates in the contract.
Regards
Nadarajah Pratheb

For a Sales order, what is Actual Delivery Date to Customer?

Hi Experts,
I am an ABAP consultant. In a particular report, for a Sales order I am asked to display:
‘Delivery Create Date (LIKP-ERDAT)’,
‘PGI Date’,
‘Requested Delivery Date (VBAK-VDATU)’ and
‘Actual Delivery Date to Customer’.
And in addition, I also have to show:
‘No: of days between Order Create Date to Delivery Create Date’,
‘No: of days between Delivery Create Date to PGI Date’,
‘No: of days between Requested Delivery Date to Actual Ship Date’ and
‘No: of days between Order Create Date to Actual Ship Date’.
I’ve searched SCN for similar questions but I couldn’t get clarity. I’ll be very grateful if somebody can explain me how to find the ‘Actual delivery date to customer’ and what is the difference between this date and ‘Billing date’. Also, please explain, the difference between ‘Delivery Create Date’ & ‘PGI’?

Hi Rashmith,
It seems the report is related to delivery. Below is the explanation for the different terms you mentioned in your question.
Delivery Create Date (LIKP-ERDAT)---- when a delivery is created with or without reference of an order system writes the date of creation time of creation and created by in the header data. Creation of delivery does not means that goods are dispatched. There are many steps further after a delivery is created before goods are dispatched. For example I have created an order, created delivery on 01.01.2014; delivery date will always be 01.01.2014.
PGI Date (LIKP-WADAT_IST)------ Post goods issue date is the date on which goods move out of the company to carrier. This is the last step of delivery. When delivery is created system derives different dates of planning; at this stage it will determine the planned PGI date (LIKP-WADAT) and when actual PGI happens system writes the date in LIKP-WADAT_IST which is actual goods issue date.
Requested delivery date (VBAK-VDATU)------When order is created for a customer he asks for a material, a quantity and a date on which he wants the goods. This date on which customer wants the goods is called requested delivery date. Based on the requested delivery date system will check feasibility of delivering the goods on the requested delivery date based on the delivery scheduling.
You can get the RDD based on the below logic.
Input the delivery number in VBFA-VBELN and VBFA-VBTYP_V and get VBFA-VBELV.
Input VBFA-VBELV in VBAK table and get the value of VDATU.
Actual Delivery Date to Customer-----Actual delivery date is Actual post goods issue date (LIKP-WADAT_IST). This is the date on which goods are issued to the customer and customer is liable for billing for the goods dispatched.
Difference between the Actual delivery date (Actual goods issue date) and billing date.
Normally as per standard SAP, once goods are moved out of the company customer is liable to be for billing for the goods dispatched. So by default in standard SAP system copies the actual goods issue date (LIKP-WADAT_IST) as billing date (VBRK-FKDAT) irrespective of the date of creation of the invoice (If delivery is goods issued on 01.01.2014 and billing document/invoice is created today i.e. 14.04.2014, system by default will take 01.01.2014 as billing date). And this is the correct practice.
However if you want the current date as the invoice creation date instead of the actual goods issue date we can control it by copy controls feature given in SAP.
So based on the copy controls setting, it may be different from the actual goods issue date/ actual delivery date.

Delivery type LR cannot be invoiced with billing type RE?

Hi,
I am refering below flow to create an return order, but face an error when creating credit billing document:
ret sale order(RE)-ret delivery(LR)-post goods receipt(stock will be restored in corresponding storage loc)---credit for return(RE)
Error msg: " Delivery type LR cannot be invoiced with billing type RE;
Check the table entries for the copying control of billing
documents and add the missing entries as necessary.
Make the appropriate settings in Customizing if you have
the authorization to do so."
So i guess i might need maintain corresponding copying control for 'delivery document to billing document'...As the source order type is LR, and target order type is RE...I checked SPRO and found there are below inputs needed. May i know what kind of data should be inputed normally??
"Copying requirements
Determ.export data
Assignment Number
Reference number"
Thank you very much!!

Hi
In standard SAP credit memo for sale returns with refrence to return order only. (RE). Thats why you are getting this error. If your requirement is to refer the delivery quantity for the credit memo then you can do any one of the following
1. Change the copy control setting for Return order to Credit memo.
    Go to VTFA transaction and select your return order type (RE) and Credit memo type (RE) and go to item category level and select your returns item category (REN) and change the billing quantity to 'D' -Delivery quantity.
    Now create your credit note with reference to your returns sale order. (not delivery). Onlly delivered quantity will be copied to the credit memo.
2. If you want to create return credit memo with reference to your return delivery then follow the first two guy's reply. Also you have to do one more setting at your return order document type (RE).
   Go to VOV8 and enter ur return order type and go to details then enter the return credit memo type in the delivery related billing field. (FKARV) in the billing section.
Regards
Shiva

In MIGO, i need to see delivery dates from the purchase order

Is there a way to see in transaction MIGO, the delivery dates from the purchase order? I hope there is some exit or BADI or BAPI or .... to perform this copy function?
We have multi-line POs for the same material with staggered delivery dates and the Warehouse needs to know which PO line to receive against.

when you enter the PO number in MIGO and hit enter, then you only get the items that can be received.
If you make sure that the PO items are created by ascending delivery date, then you can always take the first.
if you have the personal setting to display all items (even the already received ones), then you can take the first with a quantity proposal. already received items do not propose quantities.
I would ask purchasing to tell the vendor that he has to state the PO number along with the item number in all papers (delivery note, invoice).

Terms of payment -delivery date

hi
i want to make a terms of payment xx days from the delivery date. I would like to know how terms of payment will be made.
in SAP we have no date, document date, posting date, entry date.
Main point is how correct baseline date will be proposed in accounting document while invoice processing.
In my view i have only one option of manual entry Delivery date in accounting document in baseline date field. It is not possible to derive the proposed delivery date in system automatically.
In document date field while invoice processing i will enter invoice date not delivery date. Further in PO whatever payment terms i enter cannot propose delivery date in baseline field
main purpose is to derive correct due date in system.
please suggest if there is any other way out
thanks
s ap

hi S AP,
I think you can create a substitution, where the document date is substituted with the delivery date (coming from the MM document) and payment term will be calculated accordingly (baseline date based on document date). Probably some coding will be necessary (in a substitution exit), but I think this is the way to do it.
ec

Commitment-update based on periodic base, based on delivery date. FI_E008

Hi gurus:
In our system, we are using profile update 000350.
The purchase orders consume budget based on delivery date.
When posting an invoice, it is necessary that the commitment reduction
(amount type 0200) is posted with the invoice posting date and not the
delivery date of the purchase order.
This requires defining that value type 51 takes commitment update based
on periods.
By selecting the commitment update based on periods, it is not possible
to determine the period by the delivery date. System displays an error
message FI_E008.
We need commitment-update to be based on periodic base, based on the
delivery date.
Could you help me. Thanks

Hi,
I don't think it's possible: PBET implies using posting date as basis date in the most cases. Tthere are some exceptions, but they don't apply to purchase orders (v.type 51).
Regards,
Eli

Delivery tolerance (based on the delivery date)

Dear All
How to maintain delivery tolerance (based on the delivery date) in Purchasing Order
Would you help me, please
thanks
imron

YOu can try with
u2022 ST: Date variance (value x days)
The system calculates for each item the product of amount * (scheduled delivery date - date invoice entered) and compares this product with the absolute upper limit defined. This allows relatively high schedule variances for invoice items for small amounts, but only small schedule variances for invoice items for large amounts.
IN transaction code OMR6 for a company code.
IN SPRO - Materials Management -- LIV -- Incoming Invoice -- Invoice Block.

Bursting - Delivery Data Source

Hi,
I have created a template and mapped the appropriate fields in the source data. I would like to enable bursting split by customer and delivery by vendornum. I am using the following SQL
select distinct
VENDORNUM KEY,
BROKERS PDF TEMPLATE TEMPLATE,
RTF TEMPLATE_FORMAT,
CST_LOCALE LOCALE,
PDF OUTPUT_FORMAT,
EMAIL DEL_CHANNEL,
'[email protected]' PARAMETER1,
'[email protected]'PARAMETER2,
'[email protected]'PARAMETER3,
'Your Invoices' PARAMETER4,
'Hi'||CUST_FIRST_NAME||chr(13)|| 'Please find attached your
invoices.' PARAMETER5,
'true' PARAMETER6,
'[email protected]' PARAMETER7
from ext
How can I test that this does work, there are approx 150 vendors in the source data so there should be 150 PDF files generated and emailed. How can I verify and run this?
Thanks

Hi,
Thanks for the document, I can see the schedule page but there is no burst report options. Have I missed any other settings.
I have double checked that I have enabled bursting in the report too and included the split/deliver by and delivery data source.
Can anyone help
Thanks

Delivery Date And Reference Field

Hi All,
SAP Business One 2007A PL 30.
I just want to know if it is possible whilst in a Sales Order whether the delivery date can by default come in as the same date as the posting date. I know it is simple enough to press a key and then tab but just wanted to know if it was possible.
One more thing I would like to know is, is there a way to block a user from changing the reference field when you say copy from a Sales Order to a A/R Invoice?
Any help will be much appreciated.

Hi
Use this FMS and assign to the Delivery Date field. Referesh the field with when ever Posting Date Changes.
SELECT $[$10.1.DATE]
You can make use of the Data Ownership & Exceptions for the second query of urs.
Or u also can use SP for the same to avoid posting of the document in case the value is changed.
Regards
Reno

SO delivery date on A/R invoice

Similar Messages

Maybe you are looking for