Restriction on document date in FI

Dear Experts,
I need to restrict the system as follow
whenever a user run FI tcode for voucher entry, the system should not accept the entry if user entering document date greater than posting date.
I m not getting how to do this. is ther any BAdi or exit for this ???
pls guide.
Regards,
Jaspal

Hi,
Use the Functionality of FI Validation (Transaction code : OB28). Search SCN for more details.
Regards
Vinod

Similar Messages

To date for document date field in setup initialization

Hello All,
We are filling setup table for 2LIS_02_SCL and we are giving the restriction on document date in transaction oli3bw. Since there is a very large amount of data, we are restricting the start document date by 18.06.2009.
We would like to run regular deltas after initialization. So should we enter an end date ?
Can we enter 31.12.9999 as the end date ?
Please suggest the end date for the document date selection.
Thanks and Regards,
Radhika

There is no need to setup an end date on your InfoPackages because once you create and schedule the delta job for this extractor in LBWE, it will capture the deltas for you no matter the dates on the purchasing document.
When doing your initialization on BW, don't put any selections. Just do an Init w/o Data Transfer and then do concurrent Full Repair extracts using the same selection criteria you did for the setup jobs. You'll get improved throughput by doing this, especially if you execute multiple InfoPackages, with different selection criteria, in parallel.
Once you have your delta job scheduled, you can then execute a delta InfoPackage.

Restricting entry values for "document date"

We need to restrict BKPF's "document date" whereever it is entered.
This may not be a programming question per se, but programmers usually know at least as much as users do on the front end of SAP.
Users must not be allowed to enter invalid document dates (e.g. something with a year of 1204), which they currently CAN do. Is there a way to restrict this field in the table???
Here is a slice of teh data right out of the table so you can see the culprit T-codes. This must not happen:
Type     Doc. Date     TCode
SD     01/02/1201
BL     01/02/1201
SD     01/02/1201
BL     01/02/1201
SD     01/02/1201
BL     01/02/1201
SB     02/02/0211     FB50
BL     02/02/0211     FB50
BL     12/23/1022     MIGO
WE     12/23/1022     MIGO_GR
BL     05/02/1011     FB60
BL     05/02/1011     FB08
KR     05/02/1011     FB60
KR     05/02/1011     FB08
SB     05/13/0211     FB50
BL     05/13/0211     FB50
Thanks!

Hello,
As Gabriel has mentioned you can apply this check by implementing an FI Validation(Trxn. GGB0). This will take care of the trxn. when the a/c'ing doc is created manually e.g., FB* tcodes.
As you must be aware that an a/c'ing doc is created whenever a debit/credit transaction happens inside the system, e.g, GI/GR, Asset a/c'ing. For e.g., the MIGO trxns you've provided in your list.
In these cases the a/c'ing doc is generated automatically & the validation you've defined wont work! You've to implement the validation(via a BAdI, Customer Exit etc) in the respective transaction which can be cumbersome
Hope you get the basic idea.
BR,
Suhas
PS: Please don't try to modify the date on the a/c'ing doc directly via SQL statements!

Requirement to add new Document data restriction Field in OLI8BW

HI
I need to fill in Set Up Tables for 2LIS_12_VCITM (Deliveries) in source system. I want to restrict data only to past 3 years (2008-2010). Currently i dont have an option to select year in the Document Data Restriction area of the statistical set up screen. Please let me know how to add a year field in this area to restrict the data.
Thanks much.

HI
for this requirement customization is not possible.
Regards,
Chandra.

Documents & Data full ? Restrictions passcode wrong?

I'll admit that I have a slim understanding of how my iPhone 4S really works & at the risk of sounding crazy, I'll try to detail the issues I'm having that even the Apple store rep couldn't quite figure out.
Let me also preface by saying I don't understand most of the lingo & instructions posters give to remedy things. I need layperson's terms.
I have 18GB, no music, not many apps but almost 9GB taken up by documents & data. No idea why. I had never backed-up on iTunes because I didn't think it necessary since I don't have much info stored. Apple rep said he'd never seen that much space taken up by docs & data so he instructed me to back-up on iTunes, which I did. I started like 'as new phone' & when it asked me to enter codes (is passcode different from restrictions passcode?) I entered the same for both but when I went to clear out my docs & data (which came back I guess because I restored from back-up when prompted) I was told that my passcode is wrong.
This is the crazy part, and I know I'll sound like a nutjob but I have had some identity theft issues lately & since I don't know that much about how this all works, I worry & sound like a conspiracy theorist (which I am DEFINTELY not) but when I was wiping it & starting new, the screen flashed with a language like Arabic or another Middle Eastern script. I am SURE of this. I am a pretty intelligent person so I know what many languages look like & can't figure out why this would happen. Maybe this happens every time an iPhone is wiped?
Like I said, recently I have had some ID issues. My myverizon account was hacked & my name was booted off the account, my phone turned off, address changed to Michigan & upgrade used on high-end merchandise before I realized my phone was no longer working & called verizon to fix. Someone hacked into my wells fargo account & my minor child's account from the back end, stole nothing, but took our personal info such as social security number. Other things as well so I now worry who has access to what.
At any rate, this query post is multi-fold;
#1. If I enetered passcode/restrictions code info when wiping phone clean, why can't I get in?
#2. Why so much space taken up in docs & data? How can I free-up some space?
#3. Am I just being paranoid about foreign laguage upon restore?

When you sync, it does a backup first and then syncs those items you have selected in iTunes.
Perhaps these will help...
http://manuals.info.apple.com/enUS/iPhone_UserGuide.pdf
http://www.apple.com/support/itunes/
http://www.apple.com/iphone/how-to/#basics.introduction

Document date in MIGO takes any date in past and future

All SAP Gurus,
We have a problem with Document date in MIGO taking any date in past and future.
We want to restrict this date, although this (document date) has no relation with posting of the document.
Can it be done?
Regards,

Hi
Check the below message setting if it works and set it to E mode
in mm-->Purchasing->environment data-->Define Attributes of System Messages->system messages----> New entries
00 06 028 Purchase order date is in the past
For future you may have to go for an enhancement. Check out
Regards
Edited by: samuel mendis on May 22, 2009 9:02 AM

Restriction of document numbers with a formula

Hi,
Can anybody please help me in this reporting requirment..
I need to restrict the document numbers with a characteristic value(zterm) also with a condition i.e where difference between due date & report date is more than 3 days..
i need to display only the document numbers with the above..
regards,
Rajendra

Create a calculated KF which formula is
(due date - report date) > 3
This formula will have the value 1 if it's true, and 0 if false. Then, remove zeroes in your query.
If due date and report date are chars, just create 2 formulas variables.

Restriction of posting date in transaction CO11N for partial confirmations

Hi all,
 I am trying to restrict(by checking thru an exit) the posting date in co11n , for this i m using enhancement CONFPP04.
 Import parameter AFRUD_IMP IS USED.
 Now when i m putting production order no , operation activity no.(for e.g 10 , 20 etc ) and posting date IN SEL SCREEN OF CO11N
 AFRUD_IMP-BUDAT( POSTING DATE ) CONTAINS VALUE in debugging mode , hence i m getting the value of posting date
 and in that case check is written in code. This is the case of full confirmation.
 But in case of partial confirmation i have to give production order no , operation activity no , *Partial confirmed qty * and posting date , in this case the posting date value changes to 0 in the debug mode ie.
AFRUD_IMP-BUDAT is showing 0 and hence no calculation can be done base on the date.
 Our requirement is such that if there is a prd order no say X,
then in CO11N if user enters prd no X , operation activity no 10 , post date say D1
then again for prd no X , operation activity no 20 , post date of activity 20 should not be less than D1
SIMAILARY for X, ACTIVITY 30 , post date should not less than that of activity 20. and so on.
 But if partial quantity is mentioned value of AFRUD_IMP-BUDAT is becoming null.
 If anyone knows about this scenario please share.
Thanks and regards
Pankaj Gupta

Hi, In the T-code Mb31
The Posting Date which is used is when entering the document in Financial Accounting or Controlling. The fiscal year and the period for which an update of the accounts specified in the document or cost elements is made, are derived from this posting date.
When entering documents, the system checks whether the posting date entered is allowed by means of the posting period permitted.But this posting date can differ from both the entry date (day of entry into the system) and the document date (day of creation of the original document).This is for the practical purpose .
So its for the Monthly permitted and not for a day or range .
Secondly when you are saying :
"We want this default date to get freeze the moment you enter
the transaction (MB31). If you are opting for second option we want
some flexibility to change the date as required."
Both freezing and opting for changes is not possible , either one can occur .
You can freeze/display mode only the field for the T-code and the document type, but that will not solve your problem .
What i understand from the description is you want to Do GR on A particular date or GR should be allowed after a particular date . Please let me know if this is the case then there's a way around to do this that is you can do GR and Post on the dates near to your desirable dates .
cheers KP

MIRO - Posting Date and Document Date

Dear Gurus,
I have a query regarding Posting date and Document Date of Invoice Document.
I want to keep and restrict user to keep Posting Date and Document date same (current date) and want to restrict user from changing posting date, as i want to kep posting date and document date as same. Please suggest if there is any exit or any control i can implement in order to achieve this.
thanks & regards,
Prashant Rathore.

Hi
You can create a new Screen / transcation variant, in which the posting date and document date will have displau as field status.
Regards

Calculating local currency based on document date in goods receipt

We have a requirement in Poland that the local currency PLN should be calculated based on the document date when doing goods receipt, and not standard SAP posting date. I can only find note 619330 according to this requirement, but this note requires use of material ledger which we are not using. We have implemented note 574583 for the same requirement in transaction MIRO.
Since there are no notes from SAP according to the requirement in transaction MIGO, are there any enhancements available for using the document date instead for posting date when calculating local currency?
Best regards,
Terje

substitution used

I dont see 'documents & data' in settings

Why cant i see 'documents & data' in the settings in iPhone? Im trying to backup whatsapp but i have to turn on documents & data first but i don't see it in settings/iCloud

This is in my settings. No documents & data

Problem with material and document date in sales order

Hi All,
I am working in ECC 6.0 .I am facing problem with two fields when in enter in to sales order(tcode:va01)
1.A material comes automatically in line item.
2.Document date also comes as 27.03.2008 instead of todays date in each order i create.
I think its not related to configuration.I think its related to some modifications through exits or enhancement points.could someone suggest me a where to check and solve that.
Your's suggestion is appreciated.

Hi Sharad,
Check MV45AFZZ include in se38..It is a user exit for basic validation on sales...We may be able to find some code there (if screen data is predefined by code as mentioned)
Hope it helps
Regards
Byju

Regarding : Material document data and PO data do not match (Plant)

Hi Gurus,
Please go through this BAPI program.
While uploading it is giving an error ' Material document data and PO data do not match (Plant) '.
Please help regarding this issue.For all Other moment types it is working fine except this 351 moment type.
dATA: i_excel TYPE truxs_t_text_data. "work table for excel upload
DATA: BEGIN OF it_itab OCCURS 100,
 docdate(10),
 postdate(10),
 mvt_type(3), "Movement Type
 plant(4), "Plant
 lgort(4),
 pur_doc(10), "Purchase Document No
 po_item(3), "Purchase Document Item No
 material(18), "Material Number
 delnote(16),
 erfmg(13),
 uom(3),
 lfmng(13), "Quantity
 batch(10) TYPE c,
 vfdat TYPE vfdat,
 END OF it_itab.
DATA: it_goodsmvt_head TYPE TABLE OF bapi2017_gm_head_01 INITIAL SIZE 100,
 it_goodsmvt_code TYPE TABLE OF bapi2017_gm_code INITIAL SIZE 100,
 it_goodsmvt_item TYPE TABLE OF bapi2017_gm_item_create INITIAL SIZE 100.
DATA: wa_goodsmvt_head LIKE LINE OF it_goodsmvt_head,
 wa_goodsmvt_code LIKE LINE OF it_goodsmvt_code,
 wa_goodsmvt_item LIKE LINE OF it_goodsmvt_item.
DATA: w_mat_doc TYPE bapi2017_gm_head_ret-mat_doc,
 w_year TYPE bapi2017_gm_head_ret-doc_year.
DATA: BEGIN OF it_errmsg_goodsmvt OCCURS 10.
 INCLUDE STRUCTURE bapiret2.
DATA: END OF it_errmsg_goodsmvt.
DATA : obj_type LIKE bapiache09-obj_type,
 obj_key LIKE bapiache09-obj_key,
 obj_sys LIKE bapiache09-obj_sys.
DATA: v_date1 TYPE sy-datum.
DATA: v_date2 TYPE sy-datum.
DATA: w_lines TYPE i.
DATA: errflag.
SELECTION-SCREEN BEGIN OF BLOCK bk1 WITH FRAME TITLE text-100.
PARAMETERS: p_file TYPE rlgrap-filename.
SELECTION-SCREEN END OF BLOCK bk1.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 field_name = 'P_FILE'
 IMPORTING
 file_name = p_file.
Start-of-selection processing
START-OF-SELECTION.
CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
 EXPORTING
 i_line_header = 'X'
 i_tab_raw_data = i_excel
 i_filename = p_file
 TABLES
 i_tab_converted_data = it_itab[]
 EXCEPTIONS
 conversion_failed = 1
 OTHERS = 2.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
LOOP AT it_itab.
 REFRESH it_goodsmvt_head.
 REFRESH it_goodsmvt_item.
 CONCATENATE it_itab-docdate6(4) it_itab-docdate3(2) it_itab-docdate+0(2) INTO v_date1.
 CONCATENATE it_itab-postdate6(4) it_itab-postdate3(2) it_itab-postdate+0(2) INTO v_date2.
 wa_goodsmvt_head-pstng_date = v_date2.
 wa_goodsmvt_head-doc_date = v_date1.
 wa_goodsmvt_head-ref_doc_no = it_itab-delnote.
wa_goodsmvt_head-pr_uname = sy-uname.
 APPEND wa_goodsmvt_head TO it_goodsmvt_head.
Maintain it_goodsmvt_code
 wa_goodsmvt_code-gm_code = '04'.
Maintain it_goodsmvt_item
*LOOP AT it_itab.
IF wa_goodsmvt_item-po_number IS INITIAL.
 wa_goodsmvt_item-po_number = it_itab-pur_doc.
 wa_goodsmvt_item-move_type = it_itab-mvt_type.
 wa_goodsmvt_item-MOVE_PLANT = it_itab-plant.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = it_itab-material
 IMPORTING
 output = it_itab-material.
 wa_goodsmvt_item-material = it_itab-material.
 wa_goodsmvt_item-stge_loc = it_itab-lgort.
 wa_goodsmvt_item-po_item = it_itab-po_item.
 wa_goodsmvt_item-entry_qnt = it_itab-erfmg.
 wa_goodsmvt_item-ENTRY_UOM_ISO = it_itab-uom.
 wa_goodsmvt_item-po_pr_qnt = it_itab-lfmng.
 wa_goodsmvt_item-batch = it_itab-batch.
 wa_goodsmvt_item-expirydate = it_itab-vfdat.
 wa_goodsmvt_item-NO_MORE_GR = 'X'.
 wa_goodsmvt_item-mvt_ind = 'B'.
 APPEND wa_goodsmvt_item TO it_goodsmvt_item.
 CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
 EXPORTING
 goodsmvt_header = wa_goodsmvt_head
 goodsmvt_code = wa_goodsmvt_code
 IMPORTING
 materialdocument = w_mat_doc
 TABLES
 goodsmvt_item = it_goodsmvt_item
 return = it_errmsg_goodsmvt.
Process of commit work
 IF it_goodsmvt_head[] IS NOT INITIAL.
 DESCRIBE TABLE it_goodsmvt_head LINES w_lines.
 ENDIF.
 IF it_goodsmvt_item[] IS NOT INITIAL.
 DESCRIBE TABLE it_goodsmvt_item LINES w_lines.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = 'X'.
 IMPORTING
 RETURN =
 CLEAR errflag.
 READ TABLE it_errmsg_goodsmvt INDEX 1.
 IF it_errmsg_goodsmvt-type EQ 'E'.
 WRITE:/'Error in function', it_errmsg_goodsmvt-message.
 errflag = 'X'.
 ELSE.
 WRITE:/ it_errmsg_goodsmvt-message.
 ENDIF.
 IF errflag IS INITIAL.
 COMMIT WORK AND WAIT.
 IF sy-subrc NE 0.
 WRITE:/ 'Error in updating'.
 EXIT.
 ELSE.
 WRITE:/ 'Material Document created successfully and the Document Number for the Material',
 wa_goodsmvt_item-material,'is:', w_mat_doc, w_year.
 ENDIF.
 ENDIF.
 ENDIF.
ENDLOOP.

Hey,
Just wanted to post that in my case this was the error of MVT_IND field in item table. When I made it from 'B' to blank then it worked.
Mine is solved....
Thanks

Open items yet to be cleared which have 2-3 years old document date

Sap Experts,
This is my first post and would like to ask for a help .
I would like to clear all the open items which have Zero balance and belongs to Fiscal year 2007, 2008, 2009, 2010.
In F-04 T.code, When I put the document date, it does not allow me to clear it.
Please give me the best solution you think of any other alternative which is right or please provide me with steps to clear by using F-04
Your help will be greatly appreciated.
Kind regards
LSD

Thanks Atif & Sanil for your quick reply,
But the problem is when I enter the GL account, it is giving me error, stating that "there are no open items managed in Account XXXXXXXXXX". I have checked the control data in FS00 and only Line item Display is ticked.
I have recently joined this place, and the items are open from the day SAP was implemented. So they do not use Auto clearing.
Some points I am thinking below,
Q1. Does it mean that the control data must have open item to be "ticked"?
Q2. The A/c i am trying to clear is Non-current Trade receivables, so can we clear such accounts.
In terms of Clearing the data from 2007 till date,
Q3. Do I have to open the old periods or can I clear in current period.
Further info will be very helpful.
Cheers

Running Aging reports based on Document date in 2007

Hi All,
I have an issue while running the Receivables aging report in the 2007 version. The customer usually runs the reports based on the document date. Document date holds more importance in their case.
However, in the 2007 version, the aging report is totally governed by the posting date. For example, if I change the aging date, the posting date also changes to the aging date and viceversa. If I want to change the aging date to 01/31/09, the posting date u2018Tou2019 automatically changes to 01/31/09 and when we run the report, it will bring in all transactions until the posting date of 01/31/09.
But, the requirement is to leave the posting date as blank and give the document date u2018Tou2019 01/31/09. This will then pull all transactions until the document date of 01/31/09 irrespective of the posting date.
As a result, when you run the balance sheet with the document date of 01/31/09, receivables show a different balance. This discrepancy is due to the fact that AR Receivable aging report forces to keep the Aging date = Posting date.
This was not the case in SAP 2005 version where we were allowed to key in the aging date and the document date to get results based on document date.
This is very critical as they have recently upgraded from 2005 to 2007 and they are unable to reconcile the balances out of Balance sheet and Aging.
Please advise.
Thanks,
Payal

Hi Jitin,
We tried that as well but no luck. There is still a discrepency between what the aging shows and what the BS shows. When we put the Aging date as 01/31/09 and Document date as 01/3109, the posting date 'To' is automatically filled with 01/31/09, so it basically searches for all transactions with the posting date 01/31/09 and document date 01/31/09. This is not the requirement as we do not want to consider the posting date at all while running the aging.
I also have some screenshots if I can share. I am not sure if I should report this to SAP for further investigation or am I missing something here.
Thanks for your help.
Regards,
Payal
Edited by: Rui Pereira on May 1, 2009 10:48 AM

Restriction on document date in FI

Similar Messages

Maybe you are looking for