Making posting date mandatory for FCH8 transaction

Hi Friends,
Can any one of you have idea of how to make the posting date as mandatory in the transaction <b>FCH8</b> either through some configuration or using some exit?
Thanx in advance,
Ram

Hi,
Create a validation for the same through t.code:ob28
regards
Prasad

Similar Messages

Making Posting date field Mandatory in DP91 screen

Hi All,
Is it possible to make the posting date field mandatory in the DP91 screen.
Currently if the posting date is not specified, system will always consider the current date as posting date and picks the appropriate actual line items.
Is its possible to make the posting date field Mandatory through standard way or if not through exit.Pl suggest
Regards
SB

Hi All,
By Mistake I have typed wrongly.The requirement is
In DP91 screen the current date is populated in posting date to field by default. But the user want it should be empty and they will key in the date.The reason behind is if they will always raise the Billing request for the previous month and by mistake if they executed DP91 for current date it will be an issue.
Regards
sb

Posting date issue for COGI records.

Hi all,
I have one issue regarding the posting date for the records which are being cleared from COGI.
_In case of MF47 (Postprocessing for REM) following is the behaviour,_
In this if GR has happened on say 1st and due to stock un-availability components are gone to Post processing, Now when stock of component inwarded on say 20th then GI posting happens on 20th in post processing record clearance
_Now in case of COGI (Automatic goods movement : Error handling) behaviour is different,_
In this scenario if GR has happened on say 1st and due to stock un-availability components are gone to Post processing (COGI), Now when stock of component inwarded on say 20th then GI posting happens on 1st in post processing record clearance
I want same should be happened in case of COGI also, is there any note/ correction/option available??
Thanks in advance
Regards,
Vinayak.

Dear,
There are backlogs from the backflush in repetitive manufacturing. You can display these using Transaction MF47 and/or Transaction COGI. So schedule a job for program RMSERI11 on daily basis or hourly basis so it will clear the postprocessing errors.
But for some of the errors, it needs manual intervention like updating storage location, posting dates due to posting period block etc.
Hope clear to you.
Regards,
R.Brahmankar

Make purchase order lineu00B4s posting date visible from miro transaction

I have tried to add purchase order line´s posting date from "spro-Materials Management- Logistics Invoice Verification-
Incoming Invoice- Maintain Item List Variants" but I can´t.
Is it possible?
Thanks in advance.

I just checked and you're right. Amazing the posting date isn't included as std.
This might help, you'll need a development.
Screen Exit for MIRO transaction
(If you want a screen variant based on existing available use tx OLMRLIST)
Regards

Document date&Posting date Validation In MIGO Transaction

Hi,
I need to control document date should not be in future date comparing to posting date and should not be past date comparing to PO date in MIGO transaction.Pls suggest.
Regards
Mani

Dear Mani,
Goto Spro
Materials Management -> Inventory Management and Physical Inventory -> Define Attributes of System Messages
Goto Settings for System Messages and select
Version 00
Application area -- M7
Messages no -- 088 -- Document date lies in the future. (Check your entry)
Convert in Error Massage.
Regards,
PK

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

Massive data input for employees Transaction

Hi experts!
I need to perform a massive data input for employees. Iu2018ve tried with de Tx PA71 u2013 Fast entry of Time Data - but It needs a document or a manual preselecting.
Its necessary selecting ranges of personnel number in order to perform a massive data input for employees as a salary benefit or bonus for a group of employees.
Do you know that kind of transaction?
Thanks in advanced!

Hi ,
You could also use T Code : SCAT/SCEM for mass upload or deload.
You may use below method to create SCAT in ECC (This is not a Direct method)
1) Run transaction SCEM
2) Enter a CATT name
3) Click on change, prompt appears saying it doesn't exist, do you want to
create. Click yes.
4) Enter the TCODE to record.
5) Execute the TCODE and save data.
6) Back out. Click End and copy button.
7) Double-click the TCD on the left side of screen
8) Click F5 or Field Inputs Variants
9) Use black down-arrow to step through screens.
10) Double click on fields to set variables. (SAP adds leading & to each
variable name).
11) Save and back out.
12) Go to menu path Environment --> Extended CATT.
13) Click change and change type from (M) Manual Test Case to (C) CATT.
14) Assign component.
15) Click save. Back out.
16) Execute SCAT and Go to --> Variants --> Export Default and save as text
file.
17) Edit file with new test data.
18) Execute CATT.
After step 6 you can also leave SCEM and run SCAT and perform the
parameterization there as usual.
Hope this helps.
Inputs for Neeraj.

Due date grid for FP04 transaction

Hi Folks,
I need a report layout showing the due date grid for all the open items. Using FP04, I created layouts with all the required fields, but I'm unable to see the grid for due days. Few screenshots of the layout I designed and the summarization fields I defined in our system.
As shown in the output screenshot above, it doesn't display the total grid horizontally for a given customer, instead it is showing rows individually for each grid (30, 60,etc.).
Please advise how this can be fixed to show all the grids for a given customer (30, 60, 90, 180, etc.) in a single row.
Thanks in advance.
Regards,
Santosh

Hi Amlan,
Thanks for your response.
Here is the layout I have defined.
I initially had few subtotals maintained, but I removed them later as it was not working.
Please advise.
Thanks,
Santosh.

Making storage location mandatory for one plant.

Hi All ,
       I want to make storage location field mandatory in ME21N for only one plant .Like in our organisation structure two comp codes 1000 and 3000 are there .Under each comp code one plant like under 1000 1000plant is there and under 3000 3000 plant is there .I want to make storage location field mandatory for only 3000 plant during creation of PO.Is it possible ?
       Plz reply .

Hi Abhijit,
Suggestions:
        1) As per your last comment, new document type is used for doing PO for that particular plant. Check the Field Selection Group in the respective document type. (SPRO -> Materials Management -> Purchasing --> PO --> Define Document Type)
        2) Then SPRO -> Materials Management -> Purchasing --> PO --> Define Screen Layout at document level, Select the Field selection group. Then goto to Supplying plant and make the Issuing storage location as a "Mandatory field".
Note: But you can use this document type for this particular plant only. For the other plants, use the general document type.
          Please revert if you need any clarification.

MB5B - Stock on Posting Date, Specification for data base accec

Hi,
I am facing some problem with MB5B Transaction as when we login with t. code MB5B at the bottom of screen there is radio button selection for specification of database access for best runtime and the default the first radio button is selected i.e Database determines optimum access but with this report is coming very very slow we have to wait for 4 minuts for each material and same if we execute by selectting the second radio button i.e start off with material number i am getting data very fast with in 5 second so i want to know what is diffference between these radio buttons if we select first second or third radio buttons
one more thing we are facing problem from last 4 days only .
regards,
zafar

I dont have these 3 buttons in my MB5B in ECC6 system.
But I saw OSS Note 1005901 - MB5B: Performance problems
it explains why it is that slow.

Date format for call transaction

Hi,
What is the best solution for passing a date field to a call transaction in the date format that the user has in his settings?.
Rgds

The best solution is to define a character field of length 10. Then WRITE the date to the BDC_DATE and then use this variable when passing to BDC.
data: bdc_date(10) type c.
write sy-datum to bdc_Date.
Regards,
Rich Heilman

Making a field mandatory in MIRO transaction

Hi all,
I have an issue like this
In the MIRO Transaction , for credit memo , I need to make the field INV.REF. as a mandatory field.
Kindly suggest me on this .
thanks,
Sumit

Hi,
1.- in transaction OLMRLIST enter:
Transaction = MIR7
screen variant = ZWHATEVER
Program = SAPLFDCB
screen = 20
2.- click on button create (here you´ll go to transaction MIRO)
3.- Click on button "save" and a popup will appear
4.- Click on button "continue"
5.- Click on "Back" and here you will see the variant details
6.- Look for row of field "Inv.Ref." and check the checbox of column "Required"
7.- Save and activate
8.- Later on you can modify your variant too
Best regards.
Edited by: Pablo Casamayor on Apr 15, 2009 12:02 PM

Could not create a valid GL date rejection for PA transactions to GL

Hi All,
PRC: Interface Labor Costs to General Ledger has the Rejection "Could not create a valid GL date".
I have verified all Periods are Opened. Still there is a a rejection.
Thanks,
Praveen

Praveen Bharadwaj wrote:
Hi All,
PRC: Interface Labor Costs to General Ledger has the Rejection "Could not create a valid GL date".
I have verified all Periods are Opened. Still there is a a rejection.
Thanks,
PraveenPlease see these docs.
PAGGLT, PASGLT gives 'Could Not Create A Valid GLDate', even when GL data is re-open. [ID 330874.1]
PRC: Interface Labor Costs to GL (PALDLC) Will Not Interface, CDL.Batch_Name Is Null [ID 437301.1]
PALDLC and PASDUC Error - Could Not Create A Valid GL Date For Provider [ID 338330.1]
Distribute Labor Cost Exception-Could Not Create A Valid GL Date [ID 418675.1]
PAXACCPB - PRC: Create Accounting Gets Error 95325 Gl Date Not An Open Or Future Enterable Period [ID 951452.1]
Thanks,
Hussein

Making Settlement rule mandatory for creating any WBS element

Hello All,
We have an requirement that system should not allow us to save any WBS element until the settlement rule is maintained.
This we want only for WBS elements where Investment rule is not assigned.
Can alyone help me to find out if this is possible, if yes then how.
Points Assured.
Thanks & Regards,
Jatinder Bansal

Hi,
The only way it seems possible is using exists in validations.
if not try to check the status of the wbs element in a validation. function module is STATUS_CHECK. and i think the system might set a special status, if a settlement rule has been maintained for a wbs element.
Rgds
Sudhir Reddy

Making condition type mandatory for a particular po document type

I have 2 po document type namely local po and international po. i want a particular condition type ZLCS to be picked automatically as soon as the user picks the po document type.

Hi,
   You may check the condition technique through a new condition table with PO document type. You may proceed as below:
   You may append the standard MM condition structure to include the PO document type field (in structure KOMPAZ), with the help of abapers . Add the field to condition catalogue in the path: OLME - Conditions - Define Price Determination Process - Extend Field Catalog for Condition Tables.
    Now, you can create condition table with document type field in M/03. Maintain the condition table in the access sequence in M/07. Assign the access sequence to condition type in M/06. Include the condition type in pricing procedure. Maintain condition record for the condition type with required document type in MEK1.
    Check the procedure and revert back in case of any doubts.
Regards,
AKPT

Making posting date mandatory for FCH8 transaction

Similar Messages

Maybe you are looking for