Delta not generated in case of Actual Goods Issue date change in R3

Hi Gurus
In our implementation in BI Production server we are using 2LIS_12_VCHDR and 2LIS_12_VCITM
extractors where in R3 Deliveries are created first and then the PGI is done. While in BI Extractions As the data comes first time without any issue but when the PGI is done the PGI date Tech Name (WADAT_IST) gets updated in the R3 system but in RSA 7 too this delta is not getting generated. can any one tell the probable reason.
We are stuck there Early help needed.
Thanks
Shivani

Hi Shivani,
did you manage to solve your problem?
We are facing a similar issue:
- We also have both datasources active: 2LIS_12_VCITM and 2LIS_12_VCHDR
- In R/3 the following steps happened: A delivery was created and the record has issued to BW --> In PSA a request with status of good issue movement = A (correct!).
- Afterwards in R/3 the delivery has been picked and then, after 1 second, issued.
- This time the requests on the two datasource look different: in 2LIS_12_VCITM it seems like the good issue delta comes before the picking delta, so the result is that the delivery is read as still open (status of good issue movement = A Not correct!). In 2LIS_12_VCHDR, instead, is all correct: the last record in PSA refers to the good issue delta.
Change documents order in R/3 is correct, but it is not the same as the sequence in PSA of 2LIS_12_VCITM.
Can anyone help me?
Thanks in advance
Roberta

Similar Messages

Actual goods issue date required to be equal to planned goods issue date

Hi All,
Can anybody tell me on what basis does the actual goods issue date get determined and what needs to be done if we want to restrict the actuall goods issue date to be equal to the planned goods issue date?
Avinash

Avinash,
Can anybody tell me on what basis does the actual goods issue date get determined
???? It is the date that the goods are actually issued from stock, e.g. whatever the date was when the delivery was actually issued, that is the date that is normally written to this field in the delivery.
what needs to be done if we want to restrict the actual goods issue date to be equal to the planned goods issue date
That's a pretty restrictive criteria. Basically, you are telling the warehouse that they are not able to issue the goods early or late. In companies I have seen, that would constitute a lot of deliveries. Hope your customers don't need the parts....
Anyhow, the restriction would have to be against the goods issue transactions being used by the warehouse. I don't believe there is any standard configuration that creates such a restriction, so it would require custom development. If you pursue this restriction, make sure you leave yourself some kind of override.
In many companies, this problem is handled through policy and procedure. Warehouse manager simply creates a policy about early and late goods issues. The system will track discrepancies in the case the policy is not followed.
Best Regards,
DB49

Collective Invoice - Actual Goods Issue date

Hi Friends,
Collective invoice topic has been discussed many times but I didn't find exact solution to solve my issue.
From sap help and few other threads it is learnt that Billing type, Billing date, Payer, Billing unit, Terms of payment, Incoterms, Letter of credit should be same to have collective invoice. During my tests it is understood that apart from those Actual Goods Issue date (Post Goods Issue) date should be same to have collective invoice for different sales orders/deliveries. In my tests SAP didn't consider Billing date but it did consider Actual GI date. In other words, even the billing date and other requirements are same invoice split happend due to different Actual GI date. However collective invoice created even though the billing date is different but Actual GI date is same.
My user creates one sales order and one delivery for a customer once in a week (so 4 orders/deliveries in a month) and creates Invoice by end of the month with collective invoice. So based on the above tests I can ask the user to create sales orders, deliveries every week but perform Post Goods Issue month end and then create invoice so that collective invoice can be done. But the issue is they want to do the Post Goods Issue every week because the stock levels should reduce on weekly basis. So how can we create collective invoice even though the Post Goods Issue is done weekly (so Actual GI date will be different)
Any idea? Please let me know if further information required.
Thank you

Hi,
You may consider writing a routine under copying requirements so that invoice is not split even if the Actual GI date is different.
Consider the following [thread|Collective billing; for more info.
Regards,
Amit

What is the difference between delivery date and actual goods issue date?

Hi ,
Can you please tell me the difference between Delivery date and Actual goods issue date ?
Delivery data can be be greater than goods issue date?
Thanks,
Ajay

Hi Ajay,
Delivery date means its the original date on which the delivery should be done.Actual goods Issue date is the date on which goods to be delivered according to the purchase order.There can be delay in the delivery so we maintain 2 objects.
Yes delivery date can be greater than Goods Issue date.
Hope this clears
Regards
Karthik

Actual Goods Issue date and Planned Goods Issue date

Dear All
we are loading the january,08 sales invoice from the legacy system to SAP system through BDC program.
for this at the time of PGI we are using Actual GI date as month of January, 08 and keeping planned GI date as the system date and at the time of creating sales order, delivery, we are not changing the material available date, loading date, delivery date, at the item level and system taking automatically based on the current date
when doing PGI system accepting and creating PGI document and billing also creating based on this delivery.
But dose it give problem in Inventory managements and FI in future, then what would be the right procedure to uploading the back dated invoices in the system.
Please give me solution for this issue, or what we are doing is the right procedure.
Thanks In advance

For those who might come across this note, the design issue was solved by incorporating Rule Groups.
Problem:
Need to have 2 different Date references for 0calday, based on the key figures. For example for Sales key figure date it would reference to Actual GI Date. But, for Intake key figure I needed the date reference to be Planned GI date.
Solution-- applied to the transfer rules of the desired cube:
1. In the starndard rule group delete the transfer rule for the appropriate key figures. in this case (sales key figure)
2. In the same rule group map all time characteristics from the cube to Planned GI date from DSO
3. Create a new rule group in the transfer rule between the DSO and the Info Cube
4. In the new rule group, create a new rule for the appropriate key figure i.e. sales
5. In the new rule group, Map the date/week/month/fiscal period to Actual GI date
6. save/activate
This solution eliminates the need for changing the data model, which makes everything almost transparent to the report users.
Hope this helps someone.
Edited by: Babak Shafiei on Dec 12, 2008 5:23 PM
Edited by: Babak Shafiei on Dec 12, 2008 5:24 PM

Settings in Actual Goods Issue Date for Delivery Document

Hi Masters,
We have a Requirement in Which the client wants that while Creating Delivery Document through VL01N the Actual PGI Date Entered should not be before the Panned GI Date it should be only After the Planned GI Date. If the user Tries to Enter the Actual GI Date which is before the Planned GI Date the System should not Accept it and should give and Error.Please tell how to Configure this.
Thanks in Advance.

Hi,
Pls make use of Status profile for the user as well as maintain proper schedule lines
regards
DSR

Billing date(fkdat) in sales order item is not copied from Goods Issue Date

Hi All
we are facing problem at item level billing date field.This field should be filled with the GI Date in schedule lines shipping tab.
but, it(billing date) is not being filled with goods issue date but, with the required deliver date at sales order header.
Please give me a solution and the root cause. This is urgent as business is halted.
Thanks
Kumar

Lakshmipati
This is from SAP Screen
"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."
earlier it is happening as desired.i.e., billing date=GI Date.
but, as of now it is taken from the required delivery date.
Please give me solution
Kumar

LR dt to be taken as BiIlling dt instead of Actual Goods issue dt

Hi
The normal Business practice is the system takes the actual goods issue date mentioned in the delivery document as the billing date and accordingly ,the payment terms or credit days given to the customer starts from this date.
Now the requirement is
The payment terms has to be with ref to LR (lorry receipt ) date and not on Actual goods issue date, for example: If the Actual goods issue date is 15th April & the LR date is 17th april then the customers credit days has to start from 17th and not from 15th april .
Because ,in real time we do not know when the transporter will pick and deliver the goods to the customer,so if the transit time is 2 days ,then customer would be loosing the ,2 credit days and the invoice would be due on the 7th day ,where as the customer would have received the stock 5 days back and not 7days back.(if the terms of payment is say 7 days)
can any one suggest how to addresse this scenario apart from the following
1) Define the terms of payment as longer by 2days
2) Give the actual goods issue date as 2days in advance
shashi

Hi TricaC,
I'm sorry to see your friend is having problems with his BT Broadband. Please use the 'contact the mods' link in my forum profile to send in his details and we'll be happy to help. You can find the link by clicking on my username.
Thanks
Neil
BTCare Community Mod
If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
We are sorry but we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

POD confirmation date allow to give before goods issue date.

Hello ,
Would like to know that POD confirmation date process , system allows to input the pod date before the actual goods issue date in VLPOD screen as logically it should be wrong i guess as per my knowledge .i.e as soon as goods receipt by customer then only he will confirm pod , how system can allow before the actual goods issue date in VLPOD.
for eg:
1.sales order
2.delivery
3.goods issue with 23.12.2013
4.pod date can enter with 01.12.2013 and save it.
5.billing document
Please advisse your thoughts/suggestions.
Regards
venkat

hi venkat
system will take back also , there is no config control ,you have to user user exit and control it
include:   MV50AFZ1
user exit: USEREXIT_SAVE_DOCUMENT_PREPARE.
IF likp-vkorg EQ '1000'.    "
    READ TABLE XLIKP INDEX 1.
     IF XLIKP-PODAT IS NOT INITIAL AND XLIKP-WADAT_IST grater then or eq to XLIKP-PODAT
      MESSAGE e001(Z1) with xlips-VBELN. "MESSAGE DOCUMENT DATE IS BACK DATE ( CHECK YOUR ENTRY)
     ENDIF.
ENDIF.
check the ABAPER discuss with above logic
regards
sankar

How to Force JHS do not generate navigation cases for Groups?

Hello
I have already seen "Overwrite faces-config and navigation rules " property for Group in JhsApp deff .But It does not work .How Force JHS do not generate navigation cases for Groups? and another question is that how can I customize navigation case generation in JheadStart?
Thanks

Hi,
You are right: the navigation rules in the main faces-config file are overwritten, even if you uncheck these flags. Here is the solution:
If you want to preserve some of the navigation rules in the main faces config: alter the velocity template for faces-config. You can only switch off the entire generation of faces-config.xml; not individual parts.
If you want to add a special navigation rule: add it to the group faces config file.
If you want to preserve post-generation changes to the group faces config file: uncheck 'generate controller group?' or put it in the templates for that group.
Note: the flag 'Overwrite Faces-Config beans and Navigation Rules?' has become obsolete, you should only use 'Generate Controller Group?'.
Regards,
Evert-Jan de Bruin
JHeadstart Team

Generate DELVRY Idoc when Post goods issue is done in SAP

I need to generate an Idoc when post goods issue is done in SAP (outbound to SAP) .I understood that I can do this using the message control .The message type DESADV with the process code DELV will support this.
But I didnt understand how to trigger the Idoc.In the current scenario our Company is doing the post goods issue in SAP for the in three different ways.
1.Manually doing the post goods issue through the transaction VL02N
2. an Inbound Interface (using Idoc) which will do Post goods Issue in SAP
3.Another Interface using BAPI, which will, do post goods issue in SAP
I have to run my outbound interface when the post goods issue is done by all the above three ways. Can any one help me out in this?

You have to configure the output first .
You can use output type LAVA ( avaialble in Std SAP ) .
( Tcode is NACE , Select Application V2 -> Outputtypes ).
( Create condition records suitable to generate an output)
Next is ALE.
Setup a distribution Model ( for DESADV ) and all other setup for ALE i.e. Distribute Dist. Model / Generate Partner Profile .
In the Partner profile in WE20 select your partner system. Double CLick on Outbound Message DESADV ( this wd be there after you generate partner profile , if not add it here in outbound ) . On this screen goto tab MESSAGE CONTROL .
Application - V2
Message Type - LAVA
Process Code - DELV.
Now you are ready to go. The moment a PGI is done in any form an output LAVA would be proposed and processed using process code DELV.
Cheers.

Actual Goods Movement Date is missing in 2LIS_11_V_SSL

Hi
Daily we are loading the Order Delivery data from the 2LIS_11_V_SSL datasource into the Global Level DSO(ZTEST) and it is snapshot of ECC Production System . That means, only the latest data is avialable in the ZTEST DSO .
Now for some of the Sales Order's , actual goods movement date is missing in the ZTEST DSO. So i need to investigate why the actual goods movement date to missing in the ZTEST DSO .
So i want to test this datasource(2LIS_11_V_SSL ) whether it is bring the actual goods movement date or not .
So how can i test this datasource 2LIS_11_V_SSL . Do i need to populate the setup with a particular sales order number.
What is the steps for that . Please let me know .
Regards
Mohammed

Hi,
Please check the PSA data first whether the field is empty . Because sometimes if you have not added the correct key fields in the DSO,you may not get the changes. So check the PSA first. If it is empty then check the data in the ECC system . If you use the standard field for the actual goods movement date please check with the functional consultant whether the below logic is followed (extracted from help.sap.com) for those sales order missing the date .
MCEX_I_WADAT
Actual goods movement date of a delivery
Definition
This field contains the actual goods movement date of a delivery of an item order.
Use
The field is only used in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL).
There, this date is determined for one delivery at a time, and is assigned to all data records for this delivery.
In these data records, you are dealing with confirmed quantities of order schedule lines, which are assigned a corresponding delivery item as delivery.
The date is only assigned if it was entered in the associated delivery.
If the logic is correct for the sales order ,then you need to reload the data .Fill the set-up table with those missing sales orders ,and run RSA3 with the selections after the set-up table filling. Check the data again here and if you find date values,then you can run the repair full request to load the data.
Still if you miss the date ,as i said earlier please check with the functional people whether any business logic is missing .
Thanks.

Fieldes planned delivery date and actual good recipt date for SAP QUERY

Hi Gurus
I am changing sap query. I need to find two fieldes : planned delivery date and actual goods recipt date
I dont know MM tables, do you know wrhere are?
in table EKPO i don't find the fieldes.
Thanks in advance

Thank a lot!
Regards

Goods issue dates are different in sales order & delivery

Hi,
We have a situation where in sales order schedule line tab goods issue date is 21.30.2011
but in delivery the planned GI date is 28.03.2011.
There are two line item in the sales order & in both the line items all the dates are same.
Same route is there in sales order & delivery.
In delivery Item category avalability check Off is Y(Do not check avail. when reporting results of pick.request)
All the dates(delivery,loading,Transportation planning) are different .
waiting for responce.
Thanks In advence
Susrikant

goods issue date is 21.30.2011
What was the Actual GI date in delivery?? This should be the same as schedule line date.
thanks
G. Lakshmipathi

Goods Issue : Cancellation date 20071231 is before the goods issue date

While trying to reverse a Goods issue document I am getting the following error.
"Cancellation date 20071231 is before the goods issue date 20080103"
Please let me know if this is a legitimate error. Is it possible to
reverse the document for 20071231 though the goods issue date is 20080103

Hi,
Better you do the goods issue reversal as same date which is in delivery(Actual GI date if not Planned GI date),if you do it in different period then there will be problem with reconcillation of COPA reports.
the value VPRS does not match,because your orginal PGI document and cancelled PGI documents with diffrenet dates.
If you do not mine on above issue,then you can very well change the date while cancelling PGI(VL09) by changing reversal date once you click option Cancel in VL09 transaction you can see that date.
Reward if it helpful.
Regards,
Chandra

Delta not generated in case of Actual Goods Issue date change in R3

Similar Messages

Maybe you are looking for