Fields 'Work Starts On' and 'Posting Date' to be sync in IW41/IW44

Hello SAP colleagues
Does anyone knows what would be the easiest way of synchronizing fields Work Starts On (AFRUD-ISDD) with Posting Date (AFRUD-BUDAT) in t-code IW41 - PM Time Confirmation?
And in t-code IW44 Collective Confirmation fields such as Posting Date (AFRUD-BUDAT) with S.Execution (AFRUD-ISDD)
Regards,
Grzegorz

Hi ,
Try to put the defaults dates of both the fields to todays date by defaulting todays date ..do the same using user exit CONFPM01 PM/SM order conf.: Determine cust. specific default values
regrds
pushpa

Similar Messages

Confirmation - start, end and post date

Hi,
In the transaction IW41 I need a start,end and post (ISDD, IEDD and BUDAT) of the confirmation order remains the same. Any suggestions?

I guess, we can achieve by User Exits only.
CONF0001 Enhancements in order confirmation
CONFPM03 PM/SM order conf.: Cust. spec. check after op. selection
Also validate in following user exit.
CONFPM05 PM/SM order conf.: Cust. specific enhancements when saving
Regards,

Default key date, Document date and posting date needs to be changed automa

Hi Experts,
The user wants to create a variant for Foreign currency valuation, wherein the default key date, Doc date and Posting date needs to be changed every month automatically. Is it possible?
Please let me know your thoughts.
Warm regards,
Murukan Arunachalam

Hi
Please follow this process.
Only specify fields that should be changed
Select these fields by entering an X in the checkboxes
Enter a U in the UPDATEFLAG field
Always specify key fields when changing the data, including in the checkboxes
The configuration is an exception here. If this needs to be changed, you need to complete it again fully.
Maintain quantities and dates in the schedule line data.
1. Minimum entry:
You must enter the order number in the SALESDOCUMENT structure.
You must always enter key fields for changes.
You must always specify the update indicator in the ORDER_HEADER_INX.
2. Commit control:
The BAPI does not run a database Commit, which means that the application must trigger the Commit so that the changes are read to the database. To do this, use the BAPI_TRANSACTION_COMMIT BAPI.

FA-retirement-Asset value date and posting date are not in same fisc year

Hello,
I would like to post retirement in the new fiscal year but with asset value date in the previous year so that NBV is calculated correctly. It is not possible neither in ABAON nor in ABAVN with any transaction type.
I always get message 'Asset value date and posting date are not in same fiscal year'.
Is there any way how to handle this?
Thank you,
Jan

Hi,
I have tried this but the settings of our Depr keys works in the way. That if you use asset value date in the new month it will calculate depreciation for the whole month.
This means if I retire with asset value date 31.12.2008 - NBV will be calculated as at 31.12.2008.
If I retire with asset value date 1.1.2008 - NBV will be calculated as at 31.1.2009.
Thank you anyway!

How to Record HTTP Requests and POST data

Hai all..
Can anyone help me to solve this issue..
How to Record HTTP Requests and POST data by using java..
regards
Ranjith Nair

You should read about TCP and splitting data stream into packets and learn how to understand packet header to assemble stream from packets.
Actually there are few different stages:
1. detect handshake to start new empty stream within your code;
2. detect subsequent packets and assemble stream (there are counters within packet header and they will help).
After creating start of TCP stream (usually 1KB is enough) you'll be able to detect is it HTTP request/header or no and start logging or ignoring packets for this connection.

GR/IR from miro document and posting date.

Hi experts,
Is there any proper way to selecting data.
My purpose is getting GR/IR on Miro Document and Posting date basis.
THE CODE IS.
TABLES : bkpf, rseg, bseg.
DATA : BEGIN OF it_bkpf OCCURS 0.
        INCLUDE STRUCTURE bkpf.
DATA : bbelnr TYPE bkpf-belnr,
      bgjahr TYPE bkpf-gjahr.
DATA : END OF it_bkpf.
*data : it_bkpf like bkpf OCCURS 0 WITH HEADER LINE.
DATA : it_rseg LIKE rseg OCCURS 0 WITH HEADER LINE.
DATA : it_bseg LIKE bseg OCCURS 0 WITH HEADER LINE.
DATA : bbelnr TYPE bkpf-belnr.
DATA : bgjahr TYPE bkpf-gjahr.
DATA : bawkey TYPE bkpf-awkey.
data : dmbtr1 type bseg-dmbtr.
data : dmbtr2 type bseg-dmbtr.
PARAMETERS : p_budat LIKE bkpf-budat.
SELECT SINGLE * FROM bkpf
WHERE budat = p_budat
AND blart = 'RE'.
WRITE :/ bkpf-awkey(10).
WRITE :/20 'I/R'.
WRITE :/20 sy-uline(30).
SELECT * FROM bseg
WHERE belnr = bkpf-belnr
    AND gjahr = bkpf-gjahr.
IF bseg-shkzg ='H'.
    bseg-dmbtr = bseg-dmbtr * -1.
ENDIF.
    dmbtr1 = dmbtr1 + bseg-dmbtr.
WRITE :/20 bseg-belnr, bseg-dmbtr.
ENDSELECT.
bbelnr = bkpf-awkey(10).
bgjahr = bkpf-awkey+10(4).
SELECT SINGLE * FROM rseg
WHERE belnr = bbelnr
AND gjahr = bgjahr.
SKIP 2.
CONCATENATE rseg-lfbnr rseg-lfgja INTO bawkey.
SELECT SINGLE * FROM bkpf
WHERE awkey = bawkey.
WRITE :/20 'G/R'.
WRITE :/20 sy-uline(30).
SELECT * FROM bseg
WHERE belnr = bkpf-belnr
    AND gjahr = bkpf-gjahr.
IF bseg-shkzg ='H'.
    bseg-dmbtr = bseg-dmbtr * -1.
ENDIF.
    dmbtr2 = dmbtr2 + bseg-dmbtr.
WRITE :/20 bseg-belnr, bseg-dmbtr.
ENDSELECT.
dmbtr1 = dmbtr1 - dmbtr2.
skip 2.
write :/ dmbtr1.

self solved

Asset value date and posting date are not in same fiscal year

Hi,
Our business user has created an asset under an incorrect asset class, which he is trying to transfer to a new asset whcih was created under correct asset class. However system is restricting user with the error message "Asset value date and posting date are not in same fiscal year". Can you please advise me how we can proceed further with this error.
Regards,
Asam.

Hi,
To transfer one asset to another asset within a company code can be done through ABUMN only.
While doing this transfer you have enter the document date, posting date, and value date for the transaction, but all these dates should be in same fiscal year only.
In your case you must have been entered the dates for asset value date and posting date , and these two dates are in diff financial years.
Please make sure that both the dates are in same FY.
Hope this will fix your issue.
Thanks,
Srinu

GR document and posting date issue for initial stock upload are overidden

Hi all
Loading initial stock into the system using standard idoc message type MBGMCR and basic type MBGMCR02.
We are trying to post the intial stock upload with posting and document dates in past with this idoc. The Idoc is accepted with these dates but while posting the system is overiding these dates and posting the document with system date. Any clue as to what is happening?
Regards,
Amit

Hi Jurgen
I am aware about the posting being possible till the last period.
But the system over-riding the posting and document dates in the IDoc even if I chose previos day's date in the current period. The dates in the IDoc are correct to be in the past. The IDoc is accepted by the system with the document and posting dates in the past.
But dates in the document after posting are system dates. Very unsual. Please let me know the reasons.
Thanks for the reply.
Cheers,
Amit

Changing document date and posting date by SE16N

Hi All,
an user has posted some customer documents (with tax codes) with wrong document date and posting date.
I have to modify these data by se16n.
In which tables I have to fill in?
Thanks
Gandalf

Hi,
It is not advisable to change the document date and posting date. Instead, try to reverse the document and post the correct one.
Regards,
Jigar

Vendor 800040 and posting data have different withholding tax types

HI
need some help..
i ve created the lease in contract but unable to activate it... getting the following error
Vendor 800040 and posting data have different withholding tax types...
how to solve this issue,,

Hi,
could you please add the error message ID and error message number.
Thank you.
Regards, Franz

MIGO -- document date and posting date

Dear all,
When i call Tcode MIGO then by default it is picking document date and posting date as 25.8.9
I want document date as current date.....
guide me

Check your System date..
also check u have the option in the header - seting-default values in MIGO Trxn

What are Pre Database Copy and Post data base copy activity list, Pre Migration and Post Migration activity list from SAP BW 7.0 to SAP BW 7.4 SPS6.

BW on HANA : Pre Database Copy and Post data base copy activity list, Pre Migration and Post Migration activity list from SAP BW 7.0 to SAP BW 7.4 SPS6.
We are trying to copy database from SAP BW7.0 to SAP BW on HANA 7.4 SPS6 so we are in search for list of steps or activities during database copy both pre and post steps.
Along with the above we are in search of Pre and post migration steps ones database is transferred successfully from oracle to HANA on 7.4 SPS6.
Kindly help us in getting the exact course of action as requested.
Thanks and Regards,
Lavina Joshi

Hi Lavina,
try this link for starters: Upgrade and Migration - BW on HANA | SAP HANA
Points to remember are:
Preparation:
     -- Hardware Sizing
     -- Preparation of Data Centres
     -- HANA Hardware preparation
     -- System Landscape Readiness (upgrade software downloads, system readiness checks, etc)
     -- House Keeping activities on BW system (data clean up, etc)
Post Installation:
     -- Sanity checks / Preparation and License checks
     -- JAVA Configurations
     -- Infoprovider conversions
Overall Stages are described below:
# Environmental setup (HANA box)
     -- Initial system checks and Building Activities (system copy, Appln server setups, etc)
# System readiness
               - ZBW_HANA_COCKPIT Tool
               - ZBW_HANA_CHECKLIST Tool
               - ZBW_ABAP_ANALYZER Tool
               - ZBW_TRANSFORM_FINDER Tool
               - SIZING Report
               - System Clean up Activities
               - Impact of 7.4 on source system checks
               - Java Upgrade for portal
# DMO Stages
               - Preparation & Pre Migration checks
               - Execution / Migration
               - Post Migration Activities
# Testing Phase
               - Source system checks/Activities
               - System and Integration Testing
               - End to End Testing
               - Performance testing
               - Reports
               - BO reports / Interfaces
Do let me know if you require any further information.
Regards,
Naren

MIR7 - Invoice and Posting date must be = PO Date

Dear All,
In MIR7 Invoice Date and Posting date is allowed prior to PO date.
e.g.
PO Date : 21.05.2010
We can make MIR7 in back date i.e. 20.05.2010 or any back date.
How to restrict this.
We don't want to allow invoice date and Posting date < PO Date.
Thanks and Regards,
Nirav

Please check this answered link:
posting date
Invoice posting not permissible after posting MIGO
validation
miro problem
Edited by: Afshad Irani on May 23, 2010 10:39 AM

Document Date and Posting date are refelected in different ways

Hi All
stange thing is happening ::::
For a perticular company code the Document Date and Posting Date is same in FBL5N but it is different in FB03 . Any clue y it is happening this ways ????
Making me crazy ... please help.
Thanks in advance
Shweta Bhardwaj

Hi,
Pl check se16- table bkpf.
Should be the one here.
BLDAT is document date and
BUDAT is posting date.
In FBL5n / Fb03 u could do a F1 and display technical settings to ensure you compare same with same.
Reg
Hein

Error in document date and posting date

hi guru's
while doing vendor creation in XK01, i m not getting the data screens like address, ..etc.i m getting error..posting period not open". what does it mean..
What date i need to give in both fields...?
can anybody send a set of data for me to create a vendor to test for my bdc/lsmw?
can any help me step by step vendor creation in xk01,
I am getting this below....
Posting period 001 2008 is not open
Message no. F5201
Diagnosis
Period 001 of fiscal year 2008 is not open for posting for the variant of posting period 1000.
System Response
Processing cannot be continued.
Procedure
The error can have several causes. In order to eliminate the error, proceed as follows:
1. Check whether the posting date was entered correctly. The system determines the posting period by means of the date.
2. Check whether the required posting period is open for posting for the variant of posting period 1000 and account type +. Make sure that the period is open for posting.
To do this, specify a period interval in which the required period for the variant of posting period 1000 and account type + is contained.
Proceed
thanks
Edited by: Raji on Jan 23, 2008 8:21 AM
Edited by: Raji on Jan 23, 2008 8:37 AM

Goto
T.code: OB52...open the posting period for your posting period variant...
Regards
s.Baskaran

Fields 'Work Starts On' and 'Posting Date' to be sync in IW41/IW44

Similar Messages

Maybe you are looking for