Valuation area 001 posting issue

HI,
I have got this error message. System doesn't post to VA 001 prior to 20.05.2011. How can I resolve this?
Business Transaction Cat: Interest on Position Date: 01.05.2011 is before the initialization key date of valuation area 001
Message no. TPM_TRG461
Diagnosis
The business transaction ' Business Transaction Cat: Interest' with position date Position Date: 01.05.2011 should be changed or created. It occurs before the initialization key date of valuation area 001. The business transaction that posted the position value on the key date may no longer specify the correct value.
System Response
The business transaction is not transferred to valuation area 001 since it occurs before the initialization key date.
Procedure
If the position displays an incorrect book value based on the change made, you may be able to adjust the book value by manual valuation.

Hi,
Suppose I want to capture all the postings which were made starting from the issue date to Go-live date for a fixed income instrument say bond or fixed deposit then what should be the approach?
What if I keep initialization date as 01.01.2004 for all valuation areas and momentarily make update type not relevant for posting and complete all accrual/amortisation/valuation processes for the past postings and then revert back the changes made to update type. Will it help to capture entire life cycle?
Assumption is all the instruments have issue or purchase date after 01.01.2004.
Thanks
Edited by: Abhinav Sethi on Jun 1, 2011 10:40 AM
Edited by: Abhinav Sethi on Jun 1, 2011 10:41 AM

Similar Messages

How do I default valuation area to post all valuation area in TBB1 or TBB4

Dear All,
How do I default valuation area to 'Post All Valuation Area' when I run TBB1 or TBB4 or any other Treasury T-Code (that has these 2 valuation areas as option)? Currently, by default, SAP is pointing to Post Operative Area. What is required by the user is to post ALL Treasury transactions to All Valuation Areas. Therefore, they have to remember to change from 'Post Operative Area' to 'Post All Valuation Area'. If they do not change this, it will be a mistake and they have to reverse the transaction and re-post again.
We have suggested to them to use Variants but again, they have to remember to choose the correct variant when they use these T-codes. Otherwise, the same thing will happen - wrong posting -> they have to reverse and re-post. Or, is there an option where we can default a variant when they use these T-codes?
Please assist. Thanks.
Regards
Fauzi

Hi,
In all standard transactions the default option will be to post to operative valuation area only.
I can think of a round about solution. Create a variant for TBB1 and save it with name space CUS& which means it is a customer created variant and also it will be transported to other systems by default. In this variant choose the option post all valuation area.
Then create a Z transaction for TBB1 with this variant as default in SE93. Now when you execute that Z transaction you will have post all valuation areas by default.
Please let me know if you can find a better solution.
Regards,
Ravi

A) Negative Stock setting-valuation area b) Goods issue account during 201

Hi,
a) where can i find the setting for the "Negative Stock - valuation area", I beleive this is different from the plant storage location setting for negative stock and needs to be activated first.
b) I am doing a goods issue 201 aginst the cost center.Is there a way of finding the correct cost center.
Thanks
Rajiv

Hi
where can i find the setting for the "Negative Stock - valuation area", I beleive this is different from the plant storage location setting for negative stock and needs to be activated first.
You can find this in OMJ1 Transaction, apart from this in the Plant parameters also you can flag the Negative stokcs for Special stocks.
b) I am doing a goods issue 201 aginst the cost center.Is there a way of finding the correct cost center.
In OKB9 maintain the defulat cost center for the G/L account used for posting the Goods issue to cost center.
You can find the G/L account attached in OBYC, GBB transaction & genaral modifier VBR, valuation class of the material
Thanks & Regards
Kishore

Convert Operative Valuation Area to meet the New GL requirements

Hi experts,
Up to now, in our customeru2019s ECC 6 system in the treasury module, there was only one operative valuation area (001) that it is linked to SAP/FI. This operative valuation area calculates results and creates accounting entries based on the Local GAAP which is the only existing ledger in SAP/FI. Our customer wants to activate the New GL functionality in SAP/FI and moreover to have as leading ledger the (New) IFRS Ledger through the migration approach. The other ledger (secondary) will be the local GAAP ledger.
What we already know is that the operative valuation area (001) must be always linked to the leading ledger. Thus the solution for this situation will be the conversion of all the flows from the existing operative valuation area (001) to the new valuation area (002)[new Local GAAP] and after the respective customizing to initialize the IFRS balances per financial instrument to the new operative valuation are (001) [new IAS GAAP].
Could you please be kind enough to know if there is a conversion tool which can deal with this situation or there are other alternative approaches to the issue described above?
Thank you for reading it,
G.P.

Thank you all for your replies.
Our problem is not on how to activate parallel valuation areas and to perform the respective customizing settings for parallel valuation and posting.
Up till now the operative valuation area 001 u2013 (Local GAAP), (we do not have second valuation area), is linked with the current leading ledger in SAP/FI, (there is only one General Ledger in SAP/FI based on Local GAAP). From now on and after the activation in SAP/FI the New GL functionality through the migration process, the Leading Ledger in SAP/FI will be the (New) IFRS Ledger.
The operative valuation area (001) in TRM must be always linked with the primary leading ledger of SAP/FI.
The problem is in the link between the operative valuation area (001) in TRM and the Leading Ledger in SAP/FI. We cannot continue to use as operative valuation area (001) the current one that makes posting to Local GAAP ledger and SAP/FI to have as primary ledger the new one that is based on IAS GAAP.
So the question is after the activation of the parallel valuation areas how to convert the flows from the up till now operative valuation area (001) into a secondary valuation area (002) and to use as operative valuation area (001) the new one based on IFRS.
Thank you again for your replies, we would appreciate any help.

Different TRL \ Position Dates per Valuation Area

Dear experts,
I would like to ask you if there is a way when you use more than one valuation areas to have different Position/TRL dates for each valuation area.
To be more specific follow the example.
When a purchase of a bond takes place we have to take into account two different dates. Trade date e.g. 03/09/2011 and settlement date e.g. 06/09/2011. The first valuation area (001 u2013 IFRS) works with trade date accounting. This means that the position of this bond will be updated with nominal amount 100.000 EUR, the nominal of the purchase, on 03/09/2011. On the other hand the second valuation area (002-Local GAAP) works with settlement date accounting. Meaning that the position of the same bond will be updated with nominal amount 100.000 EUR on 06/09/2011. The same is for the book value and all other flows and acc. entries Realized P/L, Accruals, etc.
Can this scenario be covered from SAP Treasury and Risk Management where per valuation area we have two different position dates?
With regards,
George

Hello George,
from my own experience Position/TRL date/ settlement date is equal to posting date in SAP Treasury.
in this particular example it is 06Sep, which is according to requirements of the second valuation area (002-Local GAAP). however, if you take the first valuation area (001 u2013 IFRS), working with trade date accounting, where the position of the bond should be updated with nominal amount 100.000 EUR on 03Sept - it is also possible, although this will require manual input. I mean when you execute accounting run (trans. TBB1 ), you have to specify that circumstance in the following way:
- in the field Up to and including date you will choose 06Sept
- in the other field Posting date instead of due date you should specify 03Sept.
I'm not sure regarding the accrual calculation, whether accrual period is affected by that - you can verify that yourself - just compare accrual amounts calculated for those different valuation areas - if they are the same, then it does not counts.
hope this will help you.
Best regards,
Renatas

Processing payment in Parallel Valuation areas

Hi gurus,
from business point of view, you trigger payments only from Operative valuation area (001), which means in SAP, that:
- (step 1) first you post respective flows (TBB1), which results in some open items on Open G/L account (one clearing accont) or Customer subledger;
- (step 2) then you execute payemnt program (F111 or F110), which results in clearing of previous open item (in step 1) and creates new open item on respective bank subaccount (depends on Master data of Business partner - SI: payment details);
- (step 3) and last you receive your bank statement, representing confirmation of executed payment. Then you of course post bank account vs bank subaccount and clear the last one.
However, my question is - do you need to follow the same 3 steps for Parallel Valuation areas? Or instead at the beggining you only post to Operative Valuation area (at TBB1), when execute payment run (F111), process bank statement and only after that update Parallel Valuation areas, without steps 2 and 3 (described above). How then it's possible to achieve such functionality, that posting (TBB1) would directly affect respective bank account (vs posting over clearing account and subaccount) - do you need another posting specifications, assigned to payment relevant update types in Parallel Valuation areas and another account symbol, representing Bank account direcly or some other solutions?
Appreciate your advise.
Rgds,
Renatas

Hi Prasad,
thanks for your reply.
I pretty understand the idea of Parallel Valuation areas.
However, if you say that you don't post to GL with TTB1 (I mean those Update types are marked as not relevant for posting) in the Parallel Valuation areas, so my question is how you will get your update of GL accounts in those non-leading leadgers and create required Balance Sheet ? Let's say, you placed deposit of 1.000 EUR with some bank with start date 24/04/20XX, so TBB1 should produce such kind of posting in Leading ledger:
Debit /// Position Money market (Asset side of Balance) /// 1.000 EUR /// Posting date 24/04/20XX
Credit /// Bank clearing accoount (Asset side of Balance) /// 1.000 EUR /// Posting date 24/04/20XX
Rgds,
Renatas

Initialization of Parallel Valuation Area

Hi All,
what is initialization of parallel valuation area setting and what is the key date needs to be used here.
Regards,
Andy

Hi Ravi,
I have maintained Valution area 099 for co code XYZ, It already had valuation area 001.
step by step..gng to TRM- Tr Mgr-Gen Settngs- Acc- Org
1) define val area : 099 defined
2)assgmt of valuation areas to co code -defined new val rea for xyz ( it already had for 001)
3) *** of gen valuation class to specific class - defined here 099
4) assign position mgt proceedures- assignd the valuation class 099 for the product used
when i create the transaction it gives me following error
TRL initialization for Securities, co. code XYZ, valn area 099 is not yet
complete
in Initialization of Parallel Valuation area : it is giving Country key not defined
pls help

Assign update types to Posting Specification under valuation area

Hi Friends,
Under account determiination , in Dialog structure ( left side), there are two area for ' ASSIGN UPDATE TYPES TO POSTING SPEC ' . I had to make assignment in both the area for spot transactions FX for posting spec 11100 & 11200 and update types FX1000+ and FX2000-.
But the one grouped under 'Valuation area' is not required I think. Pl let me know if i have missed some settings. that the system is asking me to do assignment in BOTH places.
Thanks
kamala

Hi,
Normally, we customize system with single valuation area (Operative) only. You need to complete customization in Valuation area category if you are maintaining multiple valuation area under single legal entity. In case of multiple valuation area settings, it is better to give account determination setting too seperately for all VA. Generally, parallel valuation may have very few accounting like MTM valuation etc, else all update type with parallel valuation can be marked "Not relevant for positng"
Regards
Prasad AV

Valuation area issue

Valuation area not defined
Message no. ME059
While creating PO i am getting this issue
in OX14 i have checked there valuation area at plant level is maintained

Hi,
Kindly check the following.
1. Check the assignment of plants to company code.
Proceed => OX18
2. Check the configuration of the valuation level.
Proceed => OX14
3. If the assignments are correct, check the entries in table
T001W.
Proceed => SM31 Table/View V_T001K_ASSIGN
Normally raised when FUNCTION 'BWKEY_INITIAL_CHECK' issues
CALL FUNCTION 'BWKEY_INITIAL_CHECK'
T001K_NOT_FOUND or T001W_NOT_FOUND
regards,
Lalita

Material ledger is not active in valuation area S001

Dear All,
I have created a Scheduling Agreement & did the GR. When I am doing invoice posting system is throwing error as Material ledger is not active in valuation area S001
What might be wrong here ? For same material if I create PO then everything is working fine. Problem is only with SA.
regds,
CB

Hi,
Please check your Material Ledger Activation setting for the Valuation AreaC002 in T-code OMX1. The Check box for the ML activation against the Valuation Area-S001 may be ticked. After activation/ticking this box, T-code CKMSTART was not executed to complete the ML activation. If you want the activation of Material Ledger, you have to run T-code CKMSTART to complete this ML activation or Otherwise uncheck this box. I hope this step will resolve your issue.
Regards
appalas

Goods Receipt posting issue

Hi Guru,
I know it's an old question to rise but I forgot how to do it. Please help.
When doing goods receipt shows--posting only possible in periods 2006/12 and 2006/11 in company code 3000.
Thanks,Cindy

As I already inform you the solution, you can take use of either solution.
From your posting period issue, it is quiet evident that you are not working on a production client and .
Anyways, if you are on production client, then take assistance of MM & FI consultant in your team.
Solution 1:
Post your material with posting date in between 12/2006 & 11/2006.
Solution 2:
Using Tcode MMPV - Close Period for Material Master,
Provide your current date.
Radio Button - Close Period only.
Reason for selecting this radio button - Setting this indicator reduces the run-time of the period closing program by approximately 50%.
So logically speaking you have to carryout this for each & every month from 2006 to till date.
If you are doing it on your testing purpose, kindly follow following solution for your cause.
Solution 3:
Step 1. Use tcode OX18 - select the plants assigned to Company code - delete - save
Step 2. Use tcode OMSY - Enter current financial month & save.(06-2010)
Step 3. Use tcode OX18 - assign all plants to co code
Step 4. Use tcode OMWD - enter valuation area 0001.
Hope it can assist you.
Thanks & Regards
JP

Creation of depreciation area for posting of parallel currencies postings

while i am posting f-90 asset e. auqsiation its giving error massage
"Customizing inconsistency (contact your system administrator)
Message no. AC496
Diagnosis
Company code BP01 manages parallel currencies in Asset Accounting. For each area that posts automatically online to FI, you have to define one dependent depreciation area that adopts both identical values and depreciation terms from depreciation area 01, and which is assigned to currency type 60 and currency INR. There is no depreciation area of this type defined for depreciation area 01.
Procedure
Check your Customizing settings."

Hi Venkat,
Create a New Depreciation area with APC Values and Depn values identical to Value 01.
Then goto valuation> currencies
Specify the Use of Parallel Currencies> and assign the currency type and valuation view to the new depn area. tick the identical values
then goto
Define Depreciation Areas for Foreign Currencies> give the parallel currency against the depn area
Now try doing the transaction.
Please revert back if you still have any issues.
Thanks,
Vamsi

What are the post instalation steps?

hi,
i am fresher in SAP.anybody plz send me postinstalation steps.
regards,
jana

Hi All,
Rewards if useful.
Post Installation Steps For ECC 5.0
What are the post installation steps after I have installed the Central Instance and Database instance?
Initial Consistency Check
SM28
1.      Logon to the newly refreshed SAP system and run transaction SM28
2.      Ensure that no errors are reported. Otherwise, take the necessary steps to correct the problems.
Edit Batch Jobs
1.      Set the fields as follows
Job name: RDDIMPDP*
User name: *
Job Status: Released and Ready checked off, all others unchecked
Fr: 01/01/0001
To: 12/31/9999
Or after event: *
2.      Press <F8> to execute the query
3.      Highlight the first job in the list and press the <CTRL>+<F11> to change the job.
4.      Examine the Exec Target field.
a.      If the box is empty, press <F3> to exit
b.      If the box is not empty, then clear out the contents so the field is blank and press <CTRL>+<S> to save
5.      Repeat Steps 3 and 4 for each additonal job listed.
Workbench Organizer Reconfiguration
1.      Logon on to client 000 of the newly refreshed system with DDIC.
SE06
1.      Select the Database Copy or migration option
2.      Press the Post-installation Processing button.
3.      When prompted Do you want to re-install the CTS?, press the Yes button
4.      When prompted for the Source System of Database Copy?, make sure that the <SID> of the production system is selected. Press the checkmark button to continue.
5.      When prompted Change originals from PRD to QUA?, press the Yes button
6.      When prompted Delete TMS Configuration?, press the Yes button
7.      When prompted Delete old TMS configuration?, press the Yes button
8.      When prompted Delete Old Versions of transport routes?, press the No button
TMS Configuration
1.      Logon on to client 000 of the newly refreshed system.
STMS
1.      Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed
2.      The information on this screen is automatically filled out from information provided during the SAP installation and should be correct. If it correct, then enter a description for the system and press <CTRL>+S to save. Otherwise, press the Other configuration button and manually configure.
3.      From the Overview menu, select Transport Routes
4.      From the Configuration menu, select Adjust with Controller
5.      Press the Yes button when prompted if you want copy the transport routes from the controller.
Import Printers
1.      Logon on to the production client of the newly refreshed system.
STMS
2.      Press <F5> to go to the import Overview.
3.      Double click on the <SID> of the newly refresh system
4.      From the Extras menu select Other Requests, then Add.
5.      In the Transp. Request box, enter the transport number containing the printer definitions that was exported. Press <Enter> to save.
6.      Select the transport that was just added to the queue and press <CTRL>+<F11> to start the import.
7.      In the Target client box, enter the productive client of the newly created system. Press <Enter> to save.
8.      Press the <Yes> button to start the transport.
Client Configuration
SCC4
1.      From the Table view menu, select Display -> Change
2.      When warned that the table is cross-client, press the checkmark button.
3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4.      Define client as follows:
Client role: Test
Changes and transports for client-specific object: Changes without automatic recording
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
5.      Press <CTRL>+S to save.
6.      Repeat steps 4 through 6 for any additional clients
Set System Change Option
SE06
1.      Press the System Change Option button.
2.      Set the global setting to Modifiable
3.      From the Edit menu, select Software Components Modifiable
4.      From the Edit menu, select Namespaces Modifiable
5.      Press <CTRL>+S to save.
Import Users
STMS
1.      Press <F5> to go to the Import overview
2.      Double click on the <SID> of the newly refreshed system.
3.      Press <F5> to refresh the list of transports
4.      Locate the transport in the list containing the user exports done before the start of the refresh.
If the transport is NOT in the list, then from the Extras menu, select Other requests then Add.   Enter the transport number and press <Enter>. Then press the Yes button to add the transport.
5.      Highlight the transport and press the Import request icon .
6.      At the client import screen, enter the target client and then press the Import button
7.      Press <Enter> to confirm that the import will proceed
SCC7
1.      Run the Post Client Import Processing
2.      The transport number should be the same as that of the transport started in STMS
3.      Schedule the job to run in the background. Do NOT schedule it to run immediately. We need to modify the job before it can be released.
4.      Press <CTRL>+S to save.
SM37
1.      Set the fields as follows
Job name: CLIENTIMPORT*
User name: *
Job Status: All options checked
Fr: 01/01/0001
To: 12/31/9999
Or after event: *
2.      Highlight the job that was created by SCC7 and press <CTRL>+<F11> to modify the job.
3.      Press the Step button.
4.      Select the RSCLXCOP line and press <CTRL><SHIFT><F7> to modify that step.
5.      In the User box, enter the background user for that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).
6.      Press <CTRL>+S to save the changes
7.      Press <F3> to go back to the main job screen.
8.      Press the Start condition button.
9.      Press the Immediate button.
10.     Press <CTRL>+S to save the changes
11.     Press <CTRL>+S again to save all the changes to the job.
12.     Job will start immediately once saved. Press <F8> to refresh the list of jobs
13.     Continue to press <F8> every once in a while to update the status of the job. Do not continue until the job is completed sucessfully.
SCC4
1.      From the Table view menu, select Display -> Change
2.      When warned that the table is cross-client, press the checkmark button.
3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4.      Set the Protection to Protection level 1
5.      Press <CTRL>+S to save.
6.      Repeat steps 3 through 5 for any additional clients
Deleting Source System Profiles
RZ10
1.      From the Utilities menu, select Import Profiles then Of Active Servers.
(Note: All application servers of the target system must be started)
2.      If the Display Profile Check Log screen is displayed, press <F3> to leave this screen.
3.      Select the Profile field and press <F4> to bring up a list of profiles.
4.      From the list select one of the profiles associated with the source production system.
5.      From the Profile menu, select Delete, then All versions, then of a profile.
6.      When prompted, press the Yes button to delete all version of the profile
7.      When prompted to delete the file at the operating system level, press the No button.
8.      Repeat steps 3 through 7 for all additional profiles associated with the source system
Reconfigure Operation Modes
RZ04
1.      From the Operation Mode menu, select Timetable
2.      Select Normal Operation and press the Change button.
3.      Highlight 00:00 in the left hand column and press the Delete Assignment button
4.      If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button.
5.      Once all the assignments are deleted, press <CTRL>+S to save.
6.      If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable.
7.      Press <F3> to go back to the main RZ04 screen.
8.      Right click on one of the listed Operation modes and select Delete
9.      Press the Yes button to confirm the deletion.
10.     Repeat steps 8 through 9 for any additional operation modes
11.     Press <F5> to create a new operation mode.
12.     Enter a name and short description for the operation mode
13.     Press <CTRL>+S to save.
14.     Press <F6> to create a new Instance
15.     From the Settings menu, select Based on current settings, then New Instances, then Set
16.     Press <F3> to go back to the main RZ04 screen.
17.     Press the Yes button to save
18.     From the Operation Mode menu, select Timetable
19.     Select Normal Operation and press the Change button.
20.     Highlight the 00:00 at the top and press <F2>
21.     Highlight the 00:00 at the bottom and press <F2>
22.     Press the Assign button.
23.     Press <F4> to select the operation mode created above.
24.     Press <CTRL>+S to save.
Delete Update Failures
SM13
1.       Set the fields as follows
Client: *
User: *
From data: 01/01/0001
From time: 00:00:00
2.      Press <Enter> to display the list of outstanding update requests
3.      If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing <F5> to select all records, then selecting the Update Records menu, then Delete.
4.      Press the Continue button to confirm the deletion.
Delete Batch Input Sessions
SM35
1.      From the Edit menu, select Select All
2.      Press <Shift>+<F2> to delete all the batch input sessions.
3.      Press the checkmark button to confirm
4.      Press the Yes button to start the delete.
Reorganize Spool
SPAD
1.      From the Administration menu select Clean-up Spool
2.      Check all check boxes and enter 0 for minimum age
3.      Press the Execute button
4.      Once complete, press <F3> twice to get back to the main SPAD screen
5.      From the Administration menu select Check Consistency
6.      Press the Delete All button.
SP12
1.      From the TemSe database menu, select Consistency check
2.      When the check is complete, press the Delete All button.
Delete Invalid Background Control Objects
SM61
1.      Press <F8> to switch in to change mode
2.      Press the Cleanup List button.
Restrict Outgoing Email and Faxes
SCOT
1.      Double click on the green Fax entry
2.      From the Supported Address Types area, press the Set button that is beside Fax
3.      In the Address area, ADJUST AS NECESSARY
4.      Double click on the green SMTP entry
5.      From the Supported Address Types area, press the Set button that is beside Internet
6.      In the Address area, ADJUST AS NECESSARY
Adjust RFC connections.
SM59
1.      Expand the TCP/IP connections section
2.      Double click on the first entry listed
3.      Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system.
Make changes as necessary.
4.      Press the Test Connection button to test the connection
5.      Press Press <CTRL>+S and then <F3> to save and return to the list of RFCs.
6.      Repeat steps 1 through 5 for each additional RFC connection
Convert Logical Systems
Under no circumstances perform this procedure on a Production system
BDLS
1.      When warned to read the documentation, press the checkmark button.
2.      In the Old logical system name box, press <F4>.
3.      Select one of the production Logical System names that needs be changed (i.e. WIIPRD400)
4.      In the New logical system name, enter what that logical system name should be called on this newly refreshed system (i.e.WIITRN400)   Note: Ignore Error/Warning about duplicate system by clicking on the check mark.
5.      De-select the Test Run and Existence check on new names in tables options
6.      From the Program menu, select Execute in background
7.      Press the checkmark button when asked to select a spool device
8.      Press the Immediate button when asked for the schedule
9.      Press <Ctrl>+S to save
10.     Use SM37 to monitor the job
11.     When job is complete, repeat steps 2 through 10 for any additional logical system names that need to be changed.
Adjust Logical Systems names
SALE
1.      Expand Sending and Receiving Systems, then Logical Systems
2.      Click on the execute icon beside Define Logical System
3.      Press the checkmark button to confirm that the change is cross client
4.
Allow Certains Settings to be modifiable
(Refer to Note 356483 for more Details)
SM54
1.      Enter V_T001B in the Table/View box.
2.      Select the Generated Objects option.
3.      Press the Create/Change button.
4.      Enter any access keys if requested
5.      Change the Recording routine to no, or user, recording routine.
6.      Press <Ctrl>+S to save
7.      Press <Enter> if warned that you are changing a function group that doesn't belong to you.
8.      You are prompted for transport. Create a new local transport.
9.      Repeat steps 1 through 8 for the following objects. You can specify the same transport you created above.
V_T001B_GL
V_T093B_01
V_T093B_02
BSI Configuration (R3 HR Systems only)
SM59
1.      Expand TCP/IP Connections
2.      Highlight BSI70-US-TAX and press the Change button
3.      Change the program field to
<hostname>\sapmnt\<SID>\SYS\EXE\RUN\TF60SERVER.EXE
4.      Double check the target host and gateway point to the correct server
5.      Press <CTRL>+S to save
6.      Press the Test connection button to test. If the connect is not successful, take the necessary steps to resolve the issue.
SE38
1.      In the Program field, enter RPUBTCU0
2.      Press <F8> to execute
3.      Select option BSI version 7.0
4.      Press <F8> to execute
5.      BSI should return tax calculations. If there are errors, take the necessary steps to resolve.
Reconfigure DB13 schedule
DB13
1.      Using the print out created before the refresh, recreate the DB13 calendar.
Client Configuration
SCC4
1.      From the Table view menu, select Display -> Change
2.      When warned that the table is cross-client, press the checkmark button.
3.      Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4.      Define clients as follows depending on client role
Development
Client role: Customizing
Changes and transports for client-specific object: Automatic recording of changes
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Quality Assurance
Client role: Test
Changes and transports for client-specific object: No changes allowed
Client-independent object changes: No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Training
Client role: Education
Changes and transports for client-specific object: No changes allowed
Client-independent object changes: No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Sandbox
Client role: Test
Changes and transports for client-specific object: Changes without automatic recording
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
5.      Press <CTRL>+S to save.
6.      Repeat steps 4 through 6 for any additional clients
Set System Change Option
Skip this section of the system is a Development or Sandbox System.
SE06
1.      Press the System Change Option button.
2.      Set the global setting to Not Modifiable
3.      Press <CTRL>+S to save.
Release Background Jobs
Currently, all background jobs, except for system standard jobs have been placed on hold (status scheduled).
Rewards if useful.
Regards,
Pherasath

Non Valuated material accounting posting

Hi friends ,
While reading the help of NON Valuated material ...I come across the below statement.
"The stock of a given material is only managed on a quantity basis, an account assignment must be defined in the purchase order. However, this account assignment does not result in the goods receipt being posted to consumption/usage. Instead, it results in the costs being debited to the account assignment object."
From this statement , my expectation was ...
In case of VALUATED MATERIAL (like spares etc) and Account assignment K in PO , system will automatically determine the GL from OBYC against GBB / VBR keys , but here at my end system is not picking this GL in PO line item and asking me to enter the GL along with Cost center and other account assignment details.
Similar details like GL and account assignment is asked by system for NON Valuated material also.
In both cases , entered GL is getting debitted ... therefore looking for the perfect explaintaion of SAP HELP statement given above.
Regards
Shrey

Ok ...
Now my understanding is like
In case of VALUATED MATERIAL with Account Assiged PO (say K) , system will pick the GL automatically from GBB / VBR and in case of NON VALUATED MATERIAL with Account Assigned PO (Say K) , system WILL NOT pick any GL and You have enter it Manually in PO line detail (Account Assignment Tab).
AND IN BOTH CASES GL in PO Line item ( Account Assignment) will get debitted and GR/IR gets Credited at the time of MIGO.
The Only advantage of using NON VALUATED material is ...... system will also update Qty and which can issue to any cost center in future ( to track Qty ) ........
BUT IN CASE I remove "QTY UPDATE" tick from NON-VALUATED Material type ( for my valuation Area) , then I am expecting system will not update any Qty and in THAT CASE BOTH material type (VALUATED AND NON VALUATED) will behave in similar manner , except (automatic) GL determination at PO level.
is this right ?
Regards
Shrey

FC valuation not getting posted to non-leading ledger

Hi Gurus,
I need your help to resolve the following issue. We have a company code with 1st LC as EUR and 2nd LC as USD which is group currency. We have valuation area V1 assigned to the ledger group that has set-up for postings to both leadine (0L) and non-leading ledger (Z1). When I am trying to run FC valuation using transaction FAGL_FC_VAL, the valuation document gets posted to leading ledger only. There is no posting to non-leading ledger. The other ledger tab is missing in the GL view of the document confirming that the posting happened in the leading ledger only.
I have gone over lot of threads in the forum but could not figure out the issue. I would really appreciate if someone can guide me to resolve this issue.
Thanks,
Shalu

Hi Shankar
Thanks for your reply. Yes, the non-leading ledger is active and has been assigned properly to the ledger group. The set-up is working fine for all company codes except one company code. In our set-up, for all company codes, we are using a valuation area V1 with always evaluate as valuation menthod and CC curency as currency type and Group currency as additional currency. We were having some valuation issues with one company code with existing set-up as Local currency 1 was different from LC2. In order to fix that issue, I created new valuation area V3 with same valuation method and currency type but no additional currency. The ledger group and assignemnts were same. The original issue with curency valuation got resolved but the new issue appeared that the posting is happening only in the leading ledger and nothing for this company code is getting posted to non-leading ledger while running transaction FAGL_FC_VAL.
If I manually force the currency in F-02 in this company code, the posting does happen to the non-leading ledger. The issue is with automatic postings only using area V3.
Please help.
Thanks,
Shalu

Valuation area 001 posting issue

Similar Messages

Maybe you are looking for