PO doc date non modifiable as per PO doc type

Hi
Please help me out. The document date of PO is modifiable, it can be given back date and also forward date during creation of PO.
Is it possible to freeze the doc date during PO create(me21n) for a particular PO doc type wise so that doc date will always the system date for a specific PO doc type & user can change the doc date for other PO doc type
Please advise.
Thank you,
Nishit

The functionality you require is not included in the
standard system. It is not possible through customizing to change the
field selection of BEDAT (Document date) for a PO. This field is
optional entry in tr. ME21N and display only in ME22N and ME23N.
There is no configuration for Field MEPO_TOPLINE-BEDAT in OMF4, which
is the transaction where Field Selection possibilities are set in 46
releases. ME21N gives the possibility to create a PO dated in the past
or in the future. Future dates are allowed to facilitate Hold and Park
functionality.
Message 06 028 is raised to advise "Purchase order date is in the past"
this message can be set to an Error message.
Go to OLME trxn code and Select Environment Data- Define attributes for system messages and set the message 06 028 Purchase order date is in the past
and also Try this
1. Goto SHD0 transaction, create a screen variant for t-code ME21N with PO date as "Output Only" option
2. Assign this screen variant to a new transaction variant for the t-code ME21N.
3. Specify the same transaction variant name in the standard variant
4. Activate the standard variant
Next time, when ME21N is executed, the PO date field will be of display mode and user cannot change date.

Similar Messages

I have used SAP doc mgmt for years. We copied a client and now when I configure a Class to my DMS DIR and go to CV01n Additional Data NONE of the characteristic entry boxes show up. Additional Data is blank.

I have used SAP doc mgmt for years. We copied a client and now when I configure a Class to my DMS DIR and go to CV01n Additional Data NONE of the characteristic entry boxes show up. Additional Data is blank.
It appears there must be some high level setting missing in the client. I have checked all authorizations and cannot find a difference between this client and all of the other clients we have. Only this one client does not show the class characteristics in the Additional Data tab.
Any ideas of why this standard function is not working). It does not matter which DIR I config the 017 class to, nothing shows on Additional Data.

Hi,
The issue is resolved. We are working in a sandbox with Class configuration on a DMS issue related to standard class 017. There are no standard settings in SPRO - Cross-Application Components | Maintain Object Types and Class Types | for the object type DRAW that will allow "auto-populating" characteristic values as we do with VC class 300.
For whatever reason DRAW and class 017 are not configured by SAP in the same manner as class 300 for example.
We made a config entry for DRAW Class 017 VBAP. Let's just say the system did not like that.
We are exploring other options.

Schedule line in Scheduling Agreement non modifiable

Hi Friends,
I'm creating Scheduling Agreement with VA31. The issue is that Schedule line category is coming as non-modifiable. Is it standard that in Scheduling Agreement, you can not overwrite default schedule line category? In customizing for Assign Schedule line categories, Manual schedule line categories are defined, but still I can not overwrite Schedule line category in VA31. Pl suggest what can be the reason. I don't have any ABAPer at my rescue.
Thank you.

Sgr,
For Sch.Line Agreement for component suppliers,we cant change sch.line category as of normal sch.line agreement.
Based on MRP for Delivery Schedule Types (Field available in Header Data under SALES view) and item category,sch.line category will be determined.
MRP Indicator
FORECAST
JIT
A
L1
CN
B
L1
L1
C
BN
L2
D
L1
L2
E
CN
CN
However,To decide which type of delivery schedule is currently relevant for requirements and delivery, the system uses the JIT delivery schedule horizon and the material requirements planning indicator in the scheduling agreement header
Try to change the MRP Indicator available in Header data to match your requirement.
For more info,try this URL
Scheduling Agreements for Component Suppliers (SD-SLS-OA) - SAP Library
Regards
Logan

Base line date as GR Doc Date - Invoice Posting thro' MIRO

Dear All,
I have a requirement here like when i do the miro, the baseline date should be of GR doc date. So from that date it will calculate the due date. I tried the diff options like posting date, doc date and entry date from the payment term, its not picking the GR doc date. Pls let me know how can i meet this requirement ?.
regds,
CB

Dear,
As per my knowledge There is no standard configuration for this in Standard SAP.
I think you have to use Some EXITS. Take help fo ABAPER.
Regards
Utsav

GR Posting Date-not modifiable

Hi Friends,
We have business requirement to have GR posting date should always default to the current date and not modifiable. Business client does not wants anyone to receive goods in the past. Please tell me how to achieve this settings?.
Thanks
Abdul

Hi
Try Field selection for MIGO transaction
Path:SPRO-MM-IM--->field selection for header -->Select display option for doc date.
Vivek
Edited by: Vivek N on Dec 29, 2008 3:52 PM

Client Settings non modifiable for ob52, ob58 etc

Certain objects in the IMG need to be modifiable in all our clients, specifically transaction OB58 (maintain financial statement version).
Currently, any updates to the standard financial statement (for example, when a new G/L account is created and it does not fall in an existing range) have to be made in the config client and transported across. However, the Financial statement version is not real config, nor is it master data, and we should be able to update it as and when G/L accounts are created.
We can do this in Production but not in our QA clients (it says the client is non modifiable), Production client is also non modifiable but the client role is 'Production', so I presume this client role allows the changes in the operation client.
Is there anyway to modify these in a client that is non modifiable such as our QA and testing clients with making the client modifiable?
We are running ECC 5 on NW04.

.

Importance of Doc. date in a PO

Hi,
I migrated all Open (full and partial) POs from a legacy SAP system to a new SAP.
Before uploading POs to the new system, I changed the Doc Date of the uploaded POs. Will this action effect the vendor payment due dates and planned goods received date of the POs?
In other words does SAP calculate Vendor payment due dates and planned goods received dates based on the Doc date of the PO?

Hi
As per me Po is legal document and as you told you want upload data from legacy system into SAP
I guess you have send all PO to vendor and vendor recorded your Po number ( legacy Po number) and PO date for is record
now suppose you change document date and If some issue is raised then how you will tackle ? vendor Po date and your system Po date wont get match,
and I think Po date important in Reporting also
Regards
Kailas Ugale
Edited by: kailasugale on Oct 20, 2011 3:59 PM

Client non-modifiable Warning while execution of RFC

Hi All,
When we execute the RFC in our Test server, I am get following warning. This function module is trying to update the HR infotype data. As this is Test client, it is non-modifiable (from config point of view).
But why its throwing warning, when we change masterdata? Same thing is working fine in Production Server which is also non-modifiable. Please suggest the solution - Regards, Vinod
Message no. TK430
Diagnosis
The system administrator has set your logon client to the 'not modifiable' status.
Client-specific objects can not be changed in this client.
System Response
The function terminates.
Procedure
Contact the system administrator.
For more information, see the SAP Library under Change and Transport System.

Hi Sandeep,
Thanks for the reply, but I couldnt find any namespace properties for HR infotype objects.
Can you please specify the exact path.
Thanks- Vinod

Sales Area per doc and cross div per sales doc

Hello Experts,
We know that a sales doc is tied to a Sales Area.
But a Customer can be extended to n Sales Areas.
So, please confirm is it true that a customer extended to n Sales Areas can only buy from 1 sales area per sales doc.
Another related question:
Cross division sales is where a sales doc allows a customer to order products from n divisions.
But Sales doc is tied to Sales Area.
So, where is the logic?
What is so specifial about div 00 that makes it cross division? Where is the setting for this div 00 that makes it cross-division?
regards
M Russo

Hi
For better understanding of your first question regarding sales area, please read the IMG activity documentation for the customizing step "Assign sales areas to sales document types".
I guess you can find your answer for the second question regarding cross divisions is as given below:
Reference division for document types (by sales area)
Specifies a division as a reference for sales document types.
Use
You can share sales document type data between different divisions. You define sales document types in a central division and then use it as a reference division. Each division to which you assign the reference can use the same sales document types defined in the reference division. The sales document types are maintained centrally in the reference division.
Procedure
If all sales document types are allowed for all divisions, leave the field blank. Otherwise, enter the division you want to use as a reference.
Example
Division Reference division
01 01
02 01
03 01
04 04
In this example, only divisions 01 and 04 have sales document types defined. Divisions 01, 02, and 03 share the sales document types defined for division 01. Division 04 has its own sales document types. When you create a sales order in division 03, the system checks the sales document type against the types defined for division 01. You do not maintain sales document types in divisions 02 and 03, since they are never used.
Regards
Madhu

Load Rule validates, yet no data values modified

The load rule worked on a server running an NT operating system with essbase version 6.1.3. I rebuilt the application on a server running W2k with an essbase version 6.1.6. The load rule validates on the new server. The load looks as if it is loading correctly. When I check out the log file, it shows a warning number 1003035 with a message stating "No data values modified by load of this data file." Any ideas??? Creating a new load rule from scratch did not work. My next plan of attack is to check out the actual txt file to see if anything looks odd.

Have you got any record select or record reject statements in your rules?

Having a problem with dates when I send my numbers doc to excel. dates are all out and that they have to cut and paste individual entries onto their spreadsheet. Any idea how I can prevent this

having a problem with dates when I send my numbers doc to excel. dates are all out and that they have to cut and paste individual entries onto their spreadsheet. Any idea how I can prevent this.
I'm using Lion on an MBP and Numbers is the latest version

May you give more details about what is wrong with your dates ?
M…oSoft products aren't allowed on my machines but I use LibreOffice which is a clone of Office.
When I export from Numbers to Excel and open the result with LibreOffice, the dates are correctly treated.
To be precise, dates after 01/01/1904 are correctly treated. dates before 01/01/1904 are exported as strings but, as it's flagged during the export process, it's not surprising.
Yvan KOENIG (VALLAURIS, France) mardi 3 janvier 2012
iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
My iDisk is : http://public.me.com/koenigyvan
Please : Search for questions similar to your own before submitting them to the community
For iWork's applications dedicated to iOS, go to :
https://discussions.apple.com/community/app_store/iwork_for_ios

Acquire, display, and write data at 50 samples per second

I have a vi running on a PXI which samples data using two 4220's (all 4 channels) and one 6031 (only 6channels). I am acquiring data at 100 samples per second, but only need to write the data out at 50 samples per second. The data needs to be displayed at a minimum of 10samples per second. The problem is that the VI can not get 50samples per second writen to the file, it writes about 20 to 30samples per second.
I dont know if the issue is displaying the data which is holding up the writing at 50samples per second or if it is something else in the VI. I have moved the writing of the data to the outside of the while loop, but this did not help enough to reach 50samples/sec.
Is it better to change the waveform data types to dynamic waveforms? Would this increase speed of operations?
Galen
Attachments:
ATM_FrictionTests_v1.2.vi ‏375 KB

Galen,
Looking at your vi, I would recommend writing to your file in a different way. The function you are using is actually opening, writing, and then closing the file every time you call it. This greatly increases the amount of resources being used. Take a look at the Cont Acq to Spreadsheet File.vi example and note that the file is only being opened and closed once. The data is being written to the file during execution of the program, and then closed when the app is done running. The example is done in traditional DAQ but you should be able to do something similar with DAQmx. Try this and let me know if it helps.
Regards,
LA

Can we change the doc date in a purchase order ?

can we change the doc date in a purchase order ?
i have created PO with wrong dates but now want to correct it, but its not letting me do it ...why ?

I don't think DOC DATES can be changed. You can only change the posting dates of the Goods receipt and Invoice documents as that is what matter for your financial consolidation.
Regards,
Ravi
Note : Please mark the helpful answers

Free Good Qty as non modifiable field in the Sales Order Level

Dear Friends,
I have successfully done the config change for the Free Goods, But now i want make the free good line item qty as a non modifiable field in the Sales Order Level.
How can i do this.. Please advice.
Thank U,
Uwanthi

Hi
This is a standard behaviour in the system
kindly use the below program and user exitexit
MV45AFZZ and use "Userexit_filed_modification"
Regfards
Damu

Due date is showing earlier than doc. date

Hi,
I have a funny question. I have posted billing doc. in VF01 for 10000/- on 30.06.2009 payment term is 30 days from the doc. date so the due date should be 30.07.2009. Against this doc. i have posted one residual payment for 5000/- on 15.08.2009 but when i am executing customer line item report in FBL5N system is showing this residual doc. date is 15.08.2009 and due date is 30.07.2009. Why is the due date showing a earlier date than doc date? The due date should be the same day or later than doc date.
Adv. thanks to all....
Regards

Hi,
When we do a residual payment option, the new document created for the residual amount, is created with reference to the original document. When we create documents with reference, by default the baseline date of the new document is same as that of the original. You can change the base line date by double clicking on the line after simulating.
Also check if you find any options in SPRO under the open item processing in the business transaction node for Accounts receivable and Accounts payable.
Thanks and Regards,
Anit

PO doc date non modifiable as per PO doc type

Similar Messages

Maybe you are looking for