Settings in Inventory Mangaement

Hai Friends,
What are the settings we need to do in r/3 side while extracting data to the BW side.
Plz reply soon, i will assign points.
[email protected]

Hi..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e0b8dfe6-fe1c-2a10-e8bd-c7acc921f366
R / 3 Inventory... R / 3 DataSource: flag is loaded
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/93ed1695-0501-0010-b7a9-d4cc4ef26d31
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f947ba90-0201-0010-da91-e57ea624a442
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2b50ac90-0201-0010-d597-8d833833f9e0
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/308fd94c-f11c-2a10-18ae-d10ccb50c041

Similar Messages

  • NETWORK PRINTER INVENTORY IN SYSTEM CENTRE CONFIGURATION MANAGER (SCCM 2012).

    SCCM HW inventory agent runs as the ‘SYSTEM’ and cannot see the end-users network drives and printers. The following two step process will help circumvent the above stated limitation.
    1) CREATE HKEY_LOCAL_MACHINE\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS PATH IN THE REGISTRY.
    Create a SCCM package.
    The package should run as administrator.
    The package should run whether or not a user is logged on.
    POWERSHELL PACKAGE 1 (Prerequisite):
    if (!(Test-Path HKLM:\SOFTWARE\SCCMINVENTORY)) {new-item HKLM:\SOFTWARE\SCCMINVENTORY -ErrorAction SilentlyContinue}
    $perm = get-acl HKLM:\SOFTWARE\SCCMINVENTORY -ErrorAction SilentlyContinue
    $rule = New-Object System.Security.AccessControl.RegistryAccessRule("Authenticated Users","FullControl", "ContainerInherit, ObjectInherit", "InheritOnly", "Allow") -ErrorAction SilentlyContinue
    $perm.SetAccessRule($rule)
    Set-Acl -Path HKLM:\SOFTWARE\SCCMINVENTORY $perm -ErrorAction SilentlyContinue
    if (!(Test-Path HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS)) {new-item HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS -ErrorAction SilentlyContinue}
    SAVE POWERSHELL FILE AS: PrinterInvRegSetup.ps1
    SETUP THE SCCM PACKAGE/PROGRAM WITH COMMAND LINE:
    %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\PowerShell.exe -NonInteractive -WindowStyle Hidden -noprofile -ExecutionPolicy Bypass -file .\PrinterInvRegSetup.ps1
    2) CAPTURE CURRENT USER’S PRINTERS AND WRITE THOSE ENTRIES TO THE ABOVE CREATED REGISTRY KEYS.
    Create a SCCM package
    The package should be run only when a user is logged in.
    POWERSHELL PACKAGE 2 (Main):
    $printers = Get-WMIObject -class Win32_Printer -ErrorAction SilentlyContinue|select-Object -Property ServerName,ShareName,Location,DriverName,PrintProcessor,PortName,Local |Where-Object {$_.Local -ne $true}-ErrorAction SilentlyContinue
    ForEach($printer in $printers){
    $PServerName= $printer.ServerName -replace ('\\','')
    $PShareName = $printer.ShareName
    $PLocation = $printer.Location
    $PDriverName = $printer.DriverName
    $PPrintProcessor = $printer.PrintProcessor
    $PPortName = $printer.PortName
    if ((Test-Path HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS)) {
    if ((Test-Path "HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS\$PShareName on $PServerName")) {
    Remove-item "HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS\$PShareName on $PServerName" -Force -ErrorAction SilentlyContinue
    New-item "HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS\$PShareName on $PServerName" -ErrorAction SilentlyContinue
    New-ItemProperty "HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS\$PShareName on $PServerName" -Name "PrintServer" -Value $PServerName -PropertyType "String" -ErrorAction SilentlyContinue
    New-ItemProperty "HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS\$PShareName on $PServerName" -Name "PrinterQueue" -Value $PShareName -PropertyType "String" -ErrorAction SilentlyContinue
    New-ItemProperty "HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS\$PShareName on $PServerName" -Name "PrinterLocation" -Value $PLocation -PropertyType "String" -ErrorAction SilentlyContinue
    New-ItemProperty "HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS\$PShareName on $PServerName" -Name "PrinterDriver" -Value $PDriverName -PropertyType "String" -ErrorAction SilentlyContinue
    New-ItemProperty "HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS\$PShareName on $PServerName" -Name "PrintProcessor" -Value $PPrintProcessor -PropertyType "String" -ErrorAction SilentlyContinue
    New-ItemProperty "HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS\$PShareName on $PServerName" -Name "PrinterPortName" -Value $PPortName -PropertyType "String" -ErrorAction SilentlyContinue
    New-ItemProperty "HKLM:\SOFTWARE\SCCMINVENTORY\NETWORKPRINTERS\$PShareName on $PServerName" -Name "DateInventoried" -Value $(get-date) -PropertyType "String" -ErrorAction SilentlyContinue
    SAVE POWERSHELL FILE AS: NetworkPrinterInventory.ps1
    SETUP THE SCCM PACKAGE/PROGRAM WITH COMMAND LINE:
    %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\PowerShell.exe -NonInteractive -WindowStyle Hidden -noprofile -ExecutionPolicy Bypass -file .\NetworkPrinterInventory.ps1
    3) CREATE A DEPLOYMENT AND SET IT TO ‘RUN ALWAYS’ AND MAKE IT A REQUIREMENT.
    Now deploy the second package and set the first package as a prerequisite (Check the box – Always run the prerequisite package)
    The deployment should be set to run every 4 hours and ‘Always rerun’. Mark the deployment as required. 
    4) ADD THE FOLLOWING IN BETWEEN THE EXTENSION SECTION WITHIN YOUR CONFIGURATION.MOF.
    //========================
    // Added extensions Start
    //========================
    #pragma namespace ("\\\\.\\root\\cimv2")
    #pragma deleteclass("NETWORKPRINTERS", NOFAIL)
    [dynamic, provider("RegProv"), ClassContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\SCCMINVENTORY\\NETWORKPRINTERS")]
    Class NETWORKPRINTERS
    [key] string KeyName;
    [PropertyContext("PrintServer")] String PrintServer;
    [PropertyContext("PrinterQueue")] String PrinterQueue;
    [PropertyContext("PrinterLocation")] String PrinterLocation;
    [PropertyContext("PrinterDriver")] String PrinterDriver;
    [PropertyContext("PrintProcessor")] String PrintProcessor;
    [PropertyContext("PrinterPortName")] String PrinterPortName;
    [PropertyContext("DateInventoried")] String DateInventoried;
    //========================
    // Added extensions end
    //========================
    5) SAVE THE BELOW DATA INTO A FILE CALLED ‘AWESOME.MOF’.
    #pragma namespace (“\\\\.\\root\\cimv2\\SMS”)
    #pragma deleteclass(“NETWORKPRINTERS”, NOFAIL)
    [SMS_Report(TRUE),SMS_Group_Name("NETWORKPRINTERS"),SMS_Class_ID("NETWORKPRINTERS")]
    Class NETWORKPRINTERS: SMS_Class_Template
    [SMS_Report(TRUE),key] string KeyName;
    [SMS_Report(TRUE)] String PrintServer;
    [SMS_Report(TRUE)] String PrinterQueue;
    [SMS_Report(TRUE)] String PrinterLocation;
    [SMS_Report(TRUE)] String PrinterDriver;
    [SMS_Report(TRUE)] String PrintProcessor;
    [SMS_Report(TRUE)] String PrinterPortName;
    [SMS_Report(TRUE)] String DateInventoried;
    6) IMPORT ‘AWESOME.MOF’ INTO SCCM DEFAULT CLIENT SETTINGS.
    Either import the above MOF file into the Client Setting/Default Client Settings/Hardware Inventory/Classes/Import. Select the option to import every thing.
    Alternatively, if you have compiled the MOF manually on the PC, Add a new reporting class by clicking the ‘Add’ button and connecting to the PC and selecting the WMI class ‘NETWORKPRINTERS‘
    and that is it. The SCCM resource explorer should soon see the Network Printers.
    Now, this is a convoluted process but this is the only way I can inventory Network printers. Any ideas or suggestions?

    All the other ways are similar because this is a per-user setting.
    http://blogs.technet.com/b/breben/archive/2013/08/26/inventory-mapped-drives-in-configmgr-2012.aspx
    Juke Chou
    TechNet Community Support

  • Add Hardware Inventory Classes - ClientSDK

    Hi,
    I'm trying to add a new Hardware Class to SCCM 2012 but keep hitting an issue.
    The actual WMI class I'm trying to add is "CCM_Application" within "root\ccm\clientSDK".
    I can add the Hardware class by connecting to a remote client (via the connect option within the Add Hardware Classes) and it shows up in the inventory classes OK.
    But on updating the client machine policy, and start a Hardware Invetory action, the inventory fails with the following message in the InventoryAgent.log file:
    Collection: Namespace = root\ccm\clientSDK; Query = SELECT __CLASS, __PATH, __RELPATH, Id, IsMachineTarget, Revision, AllowedActions, ApplicabilityState, ConfigureState, ContentSize, Deadline, DeploymentReport, Description, EnforcePreference, ErrorCode,
    EstimatedInstallTime, EvaluationState, FileTypes, FullName, Icon, InformativeUrl, InProgressActions, InstallState, IsPreflightOnly, LastEvalTime, LastInstallTime, Name, NextUserScheduledTime, NotifyUser, OverrideServiceWindow, PercentComplete, Publisher, RebootOutsideServiceWindow,
    ReleaseDate, ResolvedState, SoftwareVersion, StartTime, SupersessionState, Type, UserUIExperience FROM CCM_Application; Timeout = 600 secs.
    Unknown error encountered processing an instance of class CCM_Application: 80041024
    If, on the client machine, I run the following command in PowerShell
    Get-WmiObject -ComputerName . -Namespace "root\ccm\clientSDK" -Query "select FullName from CCM_Application"
    I get the following error:
    Get-WmiObject : Provider is not capable of the attempted operation
    At line:1 char:1
    + Get-WmiObject -ComputerName . -Namespace "root\ccm\clientSDK" -Query "select Ful ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (:) [Get-WmiObject], ManagementException
        + FullyQualifiedErrorId : GetWMIManagementException,Microsoft.PowerShell.Commands.GetWmiObjectCommand
    But if I run the following command:
    Get-WmiObject -ComputerName . -Namespace "root\ccm\clientSDK" -Query "select * from CCM_Application" | Select FullName
    The results are returned OK.
    So it looks as though you cannot select instances but have to use select *
    The question I'm asking is that, is it possible to change the query used by SCCM so that select * is used instead of each instance?
    Thanks

    Although I agree with Jason it's a goofy request, here's a way to get some of the information back. You have to have two edits.
    Add this to the bottom of your Configuration.mof in inboxes\clifiles.src\hinv:
    [Union, ViewSources{"select * from CCM_Application"},ViewSpaces{"\\\\.\\root\\ccm\\clientsdk"}, dynamic,Provider("MS_VIEW_INSTANCE_PROVIDER")]
    class cm_ClientSDKCCMApplication
     [PropertySources{"Id"},key]     string Id;
     [PropertySources{"IsMachineTarget"},key]   boolean IsMachineTarget;
     [PropertySources{"Revision"},key]    string Revision;
     [PropertySources{"ApplicabilityState"}]  string ApplicabilityState;
     [PropertySources{"ErrorCode"}]    uint32 ErrorCode;
     [PropertySources{"FullName"}]    string FullName;
     [PropertySources{"LastEvalTime"}]    datetime LastEvalTime;
     [PropertySources{"LastInstallTime"}]    datetime LastInstallTime;
     [PropertySources{"StartTime"}]   datetime StartTime;
     [PropertySources{"UserUIExperience"}]   boolean UserUIExperience;
    In your Default Client Agent Settings, Hardware Inventory, delete whatever it is you have for this.  Save the below as "ImportThis.mof", and in Default Client Agent Settings, Hardware Inventory, Import... and import it.
    [ SMS_Report (FALSE),
      SMS_Group_Name ("ClientSDKApps"),
      SMS_Class_ID  ("ClientSDKApps"),
      SMS_Namespace (FALSE) ]
    class cm_ClientSDKCCMApplication : SMS_Class_Template
     [SMS_Report(TRUE),key]  string Id;
     [SMS_Report(TRUE),key]  boolean IsMachineTarget;
     [SMS_Report(TRUE),key]  string Revision;
     [SMS_Report(TRUE)    ]  string ApplicabilityState;
     [SMS_Report(TRUE)    ]  uint32 ErrorCode;
     [SMS_Report(TRUE)    ]  string FullName;
     [SMS_Report(TRUE)    ]  datetime LastEvalTime;
     [SMS_Report(TRUE)    ]  datetime LastInstallTime;
     [SMS_Report(TRUE)    ]  datetime StartTime;
     [SMS_Report(TRUE)    ]  boolean UserUIExperience;
    As always, monitor dataldr.log, machine policy refreshes on clients, and see what you get back. 
    Standardize. Simplify. Automate.

  • Hardware Inventory - WMI Class or Registry extend Problem (NULL Values)

    Hello guys,
    I need your help please,
    I'm New to SCCM 2012, I'm trying to extend the hardware inventory, here's the steps:
    1. Default Client Settings -> Hardware Inventory -> Set Classes,
    2. For WMI - I import Class from Workstation in the network for example Root\Cimv2\TerminalServices -> Win32_TSDeploymentSettings 
    For Registry Import i use reg2mof - then import the mof file and enable it.
    If i do anything wrong, please let me know as well,
    Now for the problem...
    I can see data in the database for one computer(record) but when i import more then one computer the database has NULL Values for most of the imported data
    i can't find any solution for this problem, if you know what to do PLEASE HELP
    Thanks
    Avshalom

    After you import the classes you need to wait for hardware inventory to occur. Then the null will change to the real data.
    For registry keys, make sure that you also add the mof edit to the configuration.mof too.
    Also remember that if a computer does not have the class it will show null.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Goods issue/receipt print out

    Hi could any body let me know the print settings for goods issue & receipts and Logistics invoice verification.
    i tried with we01 for GRN , wa01 for GI, in nace settings but could not find the result.
    pls let me know the settings.especially for sub contract components issue print settings.
    regards
    Bheemasimha
    9900163939

    hi bheema,
    Configure Automatic Postings
    In this step, you enter the system settings for Inventory Management and Invoice Verification transactions for automatic postings to G/L accounts.
    You can then check your settings using a simulation function.
    Under Further information there is a list of transactions in Materials Management and their definitions.
    What are automatic postings?
    Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
    Example:
    Posting lines are created in the following accounts in the case of a goods issue for a cost center:
    Stock account
    Consumption account
    How does the system find the relevant accounts?
    When entering the goods movement, the user does not have to enter a G/L account, since the R/3 System automatically finds the accounts to which postings are to be made using the following data:
    Chart of accounts of the company code
    If the user enters a company code or a plant when entering a transaction, the R/3 System determines the chart of accounts which is valid for the company code.
    You must define the automatic account determination individually for each chart of accounts.
    Valuation grouping code of the valuation area
    If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas.
    You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
    If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code.
    Transaction/event key (internal processing key)
    Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting. Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers.
    You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is assign the relevant G/L account to each posting transaction.
    Account grouping (only for offsetting entries, consignment liabilities, and price differences)
    Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code.
    An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting".
    Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping, that is, assign G/L accounts.
    If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key.
    Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities.
    Valuation class of material or (in case of split valuation) the valuation type
    The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials.
    You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class.
    If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.
    Requirements
    Before you maintain automatic postings, you must obtain the following information:
    1. Valuation level (plant or company code)
    Establish whether the materials are valuated at plant or at company code level
    When valuation is at plant level, the valuation area corresponds to a plant.
    When valuation is at company code level, the valuation area corresponds to a company code.
    Define valuation level
    2. Chart of accounts and valuation grouping code per valuation area
    Find out whether the valuation grouping code is active.
    Activate split valuation
    If it is not active, determine the chart of accounts assigned to each valuation area (via the company code).
    If it is active, determine the chart of accounts and the valuation grouping code assigned to each valuation area.
    Group valuation areas
    You must define a separate account determination process for chart of accounts and each valuation grouping code.
    3. Valuation class per material type
    If you wish to differentiate the account determination process for specific transactions according to valuation classes, find out which valuation classes are possible for each material type.
    Define valuation classes
    4. Account grouping for offsetting entries to stock accounts
    Under
    Define account grouping for movement types , determine for which movement types an account grouping is defined for the transaction/event keys GGB (offsetting entry to stock posting), KON (consignment liabilities) and PRD (price differences).
    Default settings
    G/L account assignments for the charts of accounts INT and the valuation grouping code 0001 are SAP standard.
    Activities
    1. Create account keys for each chart of accounts and each valuation grouping code for the individual posting transactions. To do so, proceed as follows:
    a) Call up the activity
    Configure Automatic Postings .
    The R/3 system first checks whether the valuation areas are correctly maintained. If, for example, a plant is not assigned to a company code, a dialog box and an error message appear.
    From this box, choose Continue (next entry) to continue the check.
    Choose Cancel to end the check.
    The configuration menu Automatic postings appears.
    b) Choose Goto -> Account assignment.
    A list of posting transactions in Materials Management appears. For further details of the individual transactions, see Further information.
    The Account determination indicator shows whether automatic account determination is defined for a transaction.
    c) Choose a posting transaction.
    A box appears for the first posting transaction. Here you can enter a chart of accounts.
    You can enter the following data for each transaction:
    Rules for account number assignments
    With Goto -> Rules you can enter the factors on which the account number assignments depend:
    - debit/credit indicator
    - general grouping (= account grouping)
    - valuation grouping
    - valuation class
    Posting keys for the posting lines
    Normally you do not have to change the posting keys. If you wish to use new posting keys, you have to define them in the Customizing system of Financial Accounting.
    Account number assignments
    You must assign G/L accounts for each transaction/event key (except KBS). You can assign these accounts manually or copy them from another chart of accounts via Edit -> Copy .
    If you want to differentiate posting transactions (e.g. inventory postings) according to valuation classes, you must make an account assignment for each valuation class.
    Using the posting transaction "Offsetting entry for inventory posting", you have to make an account assignment for each account grouping
    If the transaction PRD (price differences) is also dependent on the account grouping, you must create three account assignments:
    - an account assignment without account grouping
    - an account assignment with account grouping PRF
    - an account assignment with account grouping PRA
    If the transaction KON (consignment and pipeline liabilities) is also dependent on the account grouping, you must create two account assignments:
    - an account assignment without account grouping (consignment)
    - an account assignment with account grouping (pipeline)
    d) Save your settings.
    2. Then check your settings with the simulation function.
    With the simulation function, you can simulate the following:
    Inventory Management transactions
    Invoice Verification transactions
    When you enter a material or valuation class, the R/3 system determines the G/L accounts which are assigned to the corresponding posting transactions. Depending on the configuration, the SAP system checks whether the G/L account exists
    In the simulation you can compare the field selection of the movement type with that of the individual accounts and make any corrections.
    If you want to print the simulation, choose Simulation -> Report.
    To carry out the simulation, proceed as follows:
    a) Choose Settings to check the simulation defaults for
    - the application area (Invoice Verification or Inventory Management)
    - the input mode (material or valuation class)
    - account assignment
    Instructions
    b) Choose Goto -> Simulation.
    The screen for entering simulation data appears.
    c) Depending on the valuation level, enter a plant or a company code on the screen.
    d) When you simulate Inventory Management transactions, goods movements are simulated. The R/3 system suggests the first movement type for simulation. If several movements are possible with this movement type, you can select a line.
    When you simulate Invoice Verification transactions, a list appears on the screen of the possible transaction types. Select a line.
    e) Then choose Goto -> Account assignments.
    A list appears of the posting lines which can be created by the selected transaction. For each posting line, the G/L account for the debit posting as well as the G/L account for the credit posting are displayed.
    f) From this screen, choose Goto -> Movement+ to get a list of the posting lines for the next movement type or transaction type.
    If you work with valuation classes, choose Goto -> Valuation class+ to receive the simulation for the next valuation class. This function is not possible when simulating with material numbers.
    Choose Goto -> Check screen layout to compare the movement type with the G/L accounts determined by the system and make any necessary corrections.
    Note
    The simulation function does NOT obviate the need for a trial posting!
    Further Notes
    The following list shows the individual transactions with examples of how they are used:
    AG1 - No documentation currently available.
    AG2 - No documentation currently available.
    AG3 - No documentation currently available.
    Expense/revenue from consumption of consignment material (AKO)
    This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
    Expenditure/income from transfer posting (AUM)
    This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
    Provisions for subsequent (end-of-period rebate) settlement (BO1)
    If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
    Income from subsequent settlement (BO2)
    The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
    Income from subsequent settlement after actual settlement (BO3)
    If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
    Supplementary entry for stock (BSD)
    This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
    Change in stock (BSV)
    Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    Stock posting (BSX)
    This transaction is used for all postings to stock accounts. Such postings are effected, for example:
    In inventory management in the case of goods receipts to own stock and goods issues from own stock
    In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
    In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
    Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
    @1A@Caution
    Take care to ensure that:
    A stock account is not used for any transaction other than BSX
    Postings are not made to the account manually
    The account is not changed in the productive system before all stock has been booked out of it
    Otherwise differences would arise between the total stock value of the material master records and the balance on the stock account.
    Revaluation of "other" consumptions (COC)
    This transaction/event key is only relevant to Brazil. It is used if a revaluation report is used for company codes in Brazil.
    The revaluation report uses the actual prices determined by the material ledger/actual costing to:
    Revaluate costs on the basis of actual prices
    Post the price differences arising from "other" consumptions (e.g. consumption to cost center) to a collective account
    This transaction/event key is needed to post the price differences. The account specified here is posted with the price differences for "other" consumptions.
    No documentation currently available.
    Small differences, Materials Management (DIF)
    This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
    Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
    These transactions are used only if
    Purchase Account Management is active in the company code.
    Note
    Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
    Before you use this function, check whether you need to use it in your country.
    Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
    These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
    You can also enter your own transactions for delivery costs in condition types.
    External service (FRL)
    The transaction is used for goods and invoice receipts in connection with subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    External service, delivery costs (FRN)
    This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    Offsetting entry for stock posting (GBB)
    Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
    AUA: for order settlement
    AUF: for goods receipts for orders (without account assignment)
    and for order settlement if AUA is not maintained
    AUI: Subsequent adjustment of actual price from cost center directly
    to material (with account assignment)
    BSA: for initial entry of stock balances
    INV: for expenditure/income from inventory differences
    VAX: for goods issues for sales orders without
    account assignment object (the account is not a cost element)
    VAY: for goods issues for sales orders with
    account assignment object (account is a cost element)
    VBO: for consumption from stock of material provided to vendor
    VBR: for internal goods issues (for example, for cost center)
    VKA: for sales order account assignment
    (for example, for individual purchase order)
    VKP: for project account assignment (for example, for individual PO)
    VNG: for scrapping/destruction
    VQP: for sample withdrawals without account assignment
    VQY: for sample withdrawals with account assignment
    ZOB: for goods receipts without purchase orders (mvt type 501)
    ZOF: for goods receipts without production orders
    (mvt types 521 and 531)
    You can also define your own account groupings. If you intend to post goods issues for cost centers (mvt type 201) and goods issues for orders (mvt type 261) to separate consumption accounts, you can assign the account grouping ZZZ to movement type 201 and account grouping YYY to movement type 261.
    @1A@Caution
    If you use goods receipts without a purchase order in your system (movement type 501), you have to check to which accounts the account groupings are assigned ZOB
    If you expect invoices for the goods receipts, and these invoices can only be posted in Accounting, you can enter a clearing account (similar to a GR/IR clearing account though without open item management), which is cleared in Accounting when you post the vendor invoice.
    Note that the goods movement is valuated with the valuation price of the material if no external amount has been entered.
    As no account assignment has been entered in the standard system, the assigned account is not defined as a cost element. If you assign a cost element, you have to enter an account assignment via the field selection or maintain an automatic account assignment for the cost element.
    Purchase order with account assignment (KBS)
    You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
    Exchange rate differences in the case of open items (KDM)
    Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
    Differences due to exchange rate rounding, Materials Management (KDR)
    An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
    KDV - No documentation currently available.
    Consignment liabilities (KON)
    Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
    Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
    None for consignment liabilities
    PIP for pipeline liabilities
    Offsetting entry for price differences in cost object hierarchies (KTR)
    The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
    LKW - No documentation currently available.
    Price differences (PRD)
    Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
    Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
    Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
    None for goods and invoice receipts against purchase orders
    PRF for goods receipts against production orders and
    order settlement
    PRA for goods issues and other movements
    PRU for transfer postings (price differences in the case
    of external amounts)
    PRK - No documentation currently available.
    PRP - No documentation currently available.
    PRQ - No documentation currently available.
    PRV - No documentation currently available.
    PRY - No documentation currently available.
    RAP - No documentation currently available.
    RKA - No documentation currently available.
    Provision for delivery costs (RUE)
    Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
    Taxes in case of transfer posting GI/GR (TXO)
    This transaction/event key is only relevant to Brazil (nota fiscal).
    Revenue/expense from revaluation (UMB)
    This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
    Expenditure/income from revaluation (UMD)
    This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
    Unplanned delivery costs (UPF)
    Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
    Input tax, Purchasing (VST)
    Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
    Goods issue, revaluation (inflation) (WGI)
    This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
    Goods receipt, revaluation (inflation) (WGR)
    This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
    GR/IR clearing (WRX)
    Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
    Caution
    You must set the Balances in local currency only indicator for the GR/IR clearing account to enable the open items to be cleared. For more on this topic, see the field documentation.
    see the below link also
    http://209.85.175.104/search?q=cache:7FJheuTAxiQJ:help.sap.com/bp_afsv1500/CP_AFS_DE/documentation/AFS_Solution_Scope_EN_DE.docprintsettingsforgoodsissue%26receiptsandLogisticsinvoice+verification.&hl=en&ct=clnk&cd=2
    thanks
    saGAR
    REWARD ME IF USEFULL

  • SQL Error 4506 in Configuration Manager dataldr.log

    Hello,
    I noticed that every minute my Config Manager dataldr.log will display the following Hardware Inventory error related to the SMS_Inventory_Data_Loader component: 
    *** [42S21][4506][Microsoft][SQL Server Native Client 11.0][SQL Server]Column names in each view or function must be unique. Column name 'systemBIOSCharacteristicsExt0' in view or function 'v_GS_DELL_BIOSEXTENSIONS' is specified more than once. : v_GS_DELL_BIOSEXTENSIONS
    The Query related to this error is:
    Select * from SMS_StatusMessage as stat left outer join SMS_StatMsgAttributes as att on stat.recordid = att.recordid left outer join SMS_StatMsgInsStrings as ins on stat.recordid = ins.recordid WHERE (COMPONENT="SMS_INVENTORY_DATA_LOADER") AND
    (stat.Time>='2014/04/24 01:41:49.000') AND (SEVERITY=-1073741824) AND (SiteCode="SMS") AND (MachineName="SCCM.CONTOSO.COM") order by stat.Time Desc
    Under "Administration" > "Client Settings" > "Default Client Settings" > "Hardware Inventory" > "Set Classes...", there is a class called "DELL_BIOSExtensions" which may be related to
    this. 
    Has anyone seen this error before or have any idea of what could be the cause of it? I'm unsure as to how long this error has been occurring. I just know it occurs roughly every 1 minute.
    Thanks
     

    It sound like you setup a custom inventory class and sorry to say it was incorrectly done.
    How was this class added? Have you compared the WMI class to that was added to CM12?
    http://www.enhansoft.com/

  • Report on hotfix compliance ...

    SCCM 2012 Sp1
    I want to get a report on all of my workstations and check for a specific update ... KB943729. I'd like to be able to check for other KB's in the future.
    I thought that if I went to: Administration --> Client Settings --> Default Client Settings --> Hardware Inventory --> Set Classes, then searched for & selected "Quick Fix Engineering" that this would ensure that hotfix information
    would be collected from the clients.
    The report I am looking at trying to use is: (Software Updates - A Compliance) --> "Compliance 2 - Specific software update"
    Unfortunately the report comes up blank, what am I missing?  How can I get the information I am after?
    I just want to see what machines have this update and which are missing it.

    Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
    Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.
    Garth Jones | My blogs: Enhansoft and
    Old Blog site | Twitter:
    @GarthMJ

  • Mov type.

    Hi,
    While I am using T code-MB1C with mov type-561,system showing error
    that Parameters for plant PLT1 not maintained in Inventory Management.
    So please give me the solution for this.
    Thanks,
    RAsh.

    Hi,
    In IMG under
    Materials Management -> Inventory Management and Physical Inventory
    Visit [Inventory Management and Physical Inventory|http://help.sap.com/saphelp_40b/helpdata/ru/2f/72369adc56d11195100060b03c6b76/frameset.htm]
    In this section, you complete the system settings required for the following:
    print control and user maintenance
    goods movements including:
    goods issues and postings
    goods receipts
    reservations
    physical inventory
    reporting/evaluations
    transfer of data from external DP systems
    Visit [Plant parameters|http://help.sap.com/saphelp_40b/helpdata/es/2f/72369adc56d11195100060b03c6b76/frameset.htm]
    In this step, you make the general plant settings for Inventory Management. All settings are also contained in the individual steps of the Implementation Guide for Inventory Management.
    Recommendation
    SAP recommends that you do not make the plant settings here, but in the individual steps of the Implementation Guide, so that the settings here are not without a context. Dependent settings are not contained in this step.
    Activities
    If you have created a plant in the enterprise structure using the Copy plant function, you do not need to make any settings.
    If you have created a plant manually, you have to create a new entry for the plant parameters.
    Regards,
    Srilatha.

  • Account assignment

    Hi Gurus,
    I understand that TCodes OBYC and OKB9 both are for account assignments and both are used in posting to G/L accounts? Could you please help me understand why these are used? An example of a business logic would be of greate
    Many Thanks.
    Kumar

    This are the system settings for Inventory Management and Invoice Verification transactions for automatic postings to G/L accounts.
    Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
    How does the system find the relevant accounts?
    When entering the goods movement, the user does not have to enter a G/L account, since the ERP system automatically finds the accounts to which postings are to be made using the following data:
    u2022     Chart of accounts of the company code
    If the user enters a company code or a plant when entering a transaction, the ERP system determines the chart of accounts which is valid for the company code.
    You must define the automatic account determination individually for each chart of accounts.
    u2022     Valuation grouping code of the valuation area
    If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas.
    You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
    If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code.
    u2022     Transaction/event key (internal processing key)
    Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting. Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers.
    You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is assign the relevant G/L account to each posting transaction.
    u2022     Account grouping (only for offsetting entries, consignment liabilities, and price differences)
    Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code.
    An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting".
    Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping, that is, assign G/L accounts.
    If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key.
    Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities.
    u2022     Valuation class of material or (in case of split valuation) the valuation type
    The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials.
    You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class.
    If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.

  • How can I see the rest of the disk space with SCCM 2012 R2?

    I can see most the elements of PCS in the report of assets intelligence function in SCCM 2012 R2 ,except for the free disk space.
    Thus, I cannot be noticed when some servers  need more space.
    What should I do?

    Hi,
    Please check the following steps.
    SCCM Console -> Administration -> Client Settings -> Hardware Inventory -> Set classes -> Logical Disk(SMS_LogicalDisk) -> Free Space(MB)
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Item code

    Dear All,
    We have inventory settings as follows:
    1. Group
    Fruit
    2. Name
    Pineaple
    3. Code
    P001
    4.Grade
    value : 24 -> Grade A, Grade B, Grade C
    5. Price List
    Grade A, Grade B, Grade C
    I am really confusing whether I have to create itemcode P00124A or just P001, but I create UDF contains grade value 24, price list grade A, B, C and warehouse code A, B, C.
    But if the item have to downgrade because of quality decrease, I have to change its level to grade B or even C. If the quality is more and more decrease (not B or C), I have to change the item code.
    Pls give advice. Thx
    Rgd,
    Edu
    (Georgia will win)

    I am happy to hear your answer.
    I suggest to use batch no. as lot number for the item. I create UDF in category : inventory --> batch number for items named grade and then I link it to a grade value table.
    I agree with your idea :
    lots
    grade A
    grade B
    but lot number required by user is the date of the fruit receiving. So, it is important and it will be a main criteria to assess the grade value in making downgrade decision.
    Anyway, in administration module --> general settings --> tab inventory --> unique serials number by field : I choose none. What will be I choose so that the above can be applied ?
    However, what about the price list ? do you have the automation to make the unit price change automatically when the warehouse code change ?
    Pls give advice.
    Rgd,
    Steve "Edu"

  • MM-FI Intergration

    Hello SAP Experts,
    I am having difficulty understanding what 'General Modification' tab in OBYC means?
    I have defined my valuation classes for materials but am finding it difficult to actually assign accounts to transaction keys.
    Can someone please explain various material movement types and the accounts affected due to that movement and how 'general modification' comes into picture.
    I need it really badly and really urgently.
    Thanks,
    Elizaa

    Thefollowing documentation will help you in understanding the various transactions in OBYC and also in configuring the same:
    Configure Automatic Postings
    In this step, you enter the system settings for Inventory Management and Invoice Verification transactions for automatic postings to G/L accounts.
    You can then check your settings using a simulation function.
    Under Further information there is a list of transactions in Materials Management and their definitions.
    What are automatic postings?
    Postings are made to G/L accounts automatically in the case of Invoice Verification and Inventory Management transactions relevant to Financial and Cost Accounting.
    Example:
    Posting lines are created in the following accounts in the case of a goods issue for a cost center:
    Stock account
    Consumption account
    How does the system find the relevant accounts?
    When entering the goods movement, the user does not have to enter a G/L account, since the ERP system automatically finds the accounts to which postings are to be made using the following data:
    Chart of accounts of the company code
    If the user enters a company code or a plant when entering a transaction, the ERP system determines the chart of accounts which is valid for the company code.
    You must define the automatic account determination individually for each chart of accounts.
    Valuation grouping code of the valuation area
    If the automatic account determination within a chart of accounts is to run differently for certain company codes or plants (valuation areas), assign different valuation grouping codes to these valuation areas.
    You must define the automatic account determination individually for every valuation grouping code within a chart of accounts. It applies to all valuation areas which are assigned to this valuation grouping code.
    If the user enters a company code or a plant when entering a transaction, the system determines the valuation area and the valuation grouping code.
    Transaction/event key (internal processing key)
    Posting transactions are predefined for those inventory management and invoice verification transactions relevant to accounting. Posting records, which are generalized in the value string, are assigned to each relevant movement type in inventory management and each transaction in invoice verification. These contain keys for the relevant posting transaction (for example, inventory posting and consumption posting) instead of actual G/L account numbers.
    You do not have to define these transaction keys, they are determined automatically from the transaction (invoice verification) or the movement type (inventory management). All you have to do is assign the relevant G/L account to each posting transaction.
    Account grouping (only for offsetting entries, consignment liabilities, and price differences)
    Since the posting transaction "Offsetting entry for inventory posting" is used for different transactions (for example, goods issue, scrapping, physical inventory), which are assigned to different accounts (for example, consumption account, scrapping, expense/income from inventory differences), it is necessary to divide the posting transaction according to a further key: account grouping code.
    An account grouping is assigned to each movement type in inventory management which uses the posting transaction "Offsetting entry for inventory posting".
    Under the posting transaction "Offsetting entry for inventory posting", you must assign G/L accounts for every account grouping, that is, assign G/L accounts.
    If you wish to post price differences to different price difference accounts in the case of goods receipts for purchase orders, goods receipts for orders, or other movements, you can define different account grouping codes for the transaction key.
    Using the account grouping, you can also have different accounts for consignment liabilities and pipeline liabilities.
    Valuation class of material or (in case of split valuation) the valuation type
    The valuation class allows you to define automatic account determination that is dependent on the material. for example: you post a goods receipt of a raw material to a different stock account than if the goods receipt were for trading goods, even though the user enters the same transaction for both materials.
    You can achieve this by assigning different valuation classes to the materials and by assigning different G/L accounts to the posting transaction for every valuation class.
    If you do not want to differentiate according to valuation classes you do not have to maintain a valuation class for a transaction.
    Requirements
    Before you maintain automatic postings, you must obtain the following information:
    1. Valuation level ( plant or company code)
    Establish whether the materials are valuated at plant or at company code level
    When valuation is at plant level, the valuation area corresponds to a plant.
    When valuation is at company code level, the valuation area corresponds to a company code.
    Define valuation level
    2. Chart of accounts and valuation grouping code per valuation area
    Find out whether the valuation grouping code is active.
    Activate split valuation
    If it is not active, determine the chart of accounts assigned to each valuation area (via the company code).
    If it is active, determine the chart of accounts and the valuation grouping code assigned to each valuation area.
    Group valuation areas
    You must define a separate account determination process for chart of accounts and each valuation grouping code.
    3. Valuation class per material type
    If you wish to differentiate the account determination process for specific transactions according to valuation classes, find out which valuation classes are possible for each material type.
    Define valuation classes
    4. Account grouping for offsetting entries to stock accounts
    Under Define account grouping for movement types, determine for which movement types an account grouping is defined for the transaction/event keys GGB (offsetting entry to stock posting), KON (consignment liabilities) and PRD (price differences).
    Default settings
    G/L account assignments for the charts of accounts INT and the valuation grouping code 0001 are SAP standard.
    Activities
    1. Create account keys for each chart of accounts and each valuation grouping code for the individual posting transactions. To do so, proceed as follows:
    a) Call up the activity Configure Automatic Postings.
    The ERP system first checks whether the valuation areas are correctly maintained. If, for example, a plant is not assigned to a company code, a dialog box and an error message appear.
    From this box, choose Continue (next entry) to continue the check.
    Choose Cancel to end the check.
    The configuration menu Automatic postings appears.
    b) Choose Goto -> Account assignment.
    A list of posting transactions in Materials Management The Account determination indicator shows whether automatic account determination is defined for a transaction.
    c) Choose a posting transaction.
    A box appears for the first posting transaction. Here you can enter a chart of accounts.
    You can enter the following data for each transaction:
    Rules for account number assignments
    With Goto -> Rules you can enter the factors on which the account number assignments depend:
    - debit/credit indicator
    - general grouping (= account grouping)
    - valuation grouping
    - valuation class
    Posting keys for the posting lines
    Normally you do not have to change the posting keys.  If you wish to use new posting keys, you have to define them in the Customizing system of Financial Accounting.
    Account number assignments
    You must assign G/L accounts for each transaction/event key (except KBS). You can assign these accounts manually or copy them from another chart of accounts via Edit -> Copy.
    If you want to differentiate posting transactions (e.g. inventory postings) according to valuation classes, you must make an account assignment for each valuation class.
    Using the posting transaction "Offsetting entry for inventory posting", you have to make an account assignment for each account grouping
    If the transaction PRD (price differences) is also dependent on the account grouping, you must create three account assignments:
    - an account assignment without account grouping
    - an account assignment with account grouping PRF
    - an account assignment with account grouping PRA
    If the transaction KON (consignment and pipeline liabilities) is also dependent on the account grouping, you must create two account assignments:
    - an account assignment without account grouping (consignment)
    - an account assignment with account grouping (pipeline)
    d) Save your settings.
    2. Then check your settings with the simulation function.
    With the simulation function, you can simulate the following:
    Inventory Management transactions
    Invoice Verification transactions
    When you enter a material or valuation class, the ERP system determines the G/L accounts which are assigned to the corresponding posting transactions. Depending on the configuration, the SAP system checks whether the G/L account exists
    In the simulation you can compare the field selection of the movement type with that of the individual accounts and make any corrections.
    If you want to print the simulation, choose Simulation -> Report.
    To carry out the simulation, proceed as follows:
    a) Choose Settings to check the simulation defaults for
    - the application area (Invoice Verification or Inventory Management)
    - the input mode (material or valuation class)
    - account assignment
    Instructions
    b) Choose Goto -> Simulation.
    The screen for entering simulation data appears.
    c) Depending on the valuation level, enter a plant or a company code on the screen.
    d) When you simulate Inventory Management transactions, goods movements are simulated. The ERP system suggests the first movement type for simulation. If several movements are possible with this movement type, you can select a line.
    When you simulate Invoice Verification transactions, a list appears on the screen of the possible transaction types. Select a line.
    e) Then choose Goto -> Account assignments.
    A list appears of the posting lines which can be created by the selected transaction. For each posting line, the G/L account for the debit posting as well as the G/L account for the credit posting are displayed.
    f) From this screen, choose Goto -> Movement+ to get a list of the posting lines for the next movement type or transaction type.
    If you work with valuation classes, choose Goto -> Valuation class+ to receive the simulation for the next valuation class. This function is not possible when simulating with material numbers.
    Choose Goto -> Check screen layout to compare the movement type with the G/L accounts determined by the system and make any necessary corrections.
    Note
    The simulation function does NOT obviate the need for a trial posting!
    Further notes
    The following list shows the individual transactions with examples of how they are used. The transaction/event key is specified in brackets.
    Agency business: income (AG1)
    This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.
    Agency business: turnover (AG2)
    This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.
    Agency business: expense (AG3)
    This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.
    Expense/revenue from consumption of consignment material (AKO)
    This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.
    Expenditure/income from transfer posting (AUM)
    This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.
    Provisions for subsequent (end-of-period rebate) settlement (BO1
    If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.
    Income from subsequent settlement (BO2)
    The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.
    Income from subsequent settlement after actual settlement (BO3)
    If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.
    Supplementary entry for stock (BSD)
    This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.
    Change in stock (BSV)
    Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    Stock posting (BSX)
    This transaction is used for all postings to stock accounts. Such postings are effected, for example:
    In inventory management in the case of goods receipts to own stock and goods issues from own stock
    In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
    In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt
    Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.
    Caution
    Take care to ensure that:
    A stock account is not used for any transaction other than BSX
    Postings are not made to the account manually
    The account is not changed in the productive system before all stock has been booked out of it
    Otherwise differences would arise between the total stock value of the material master records and the balance on the stock account.
    Account determination of valuated sales order stock and project stock
    Note that for valuated sales order stock and project stock (special stock E and Q) and for the transaction/event keys BSX and GBB, you must maintain an account determination to avoid receiving warning messages when entering data (purchase order or transfer posting) for valuated stock.
    During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if you enter the data for valuated stock at a later point in time.
    Revaluation of other consumption (COC)
    This transaction/event key is required for the revaluation of consumption in Actual Costing/Material Ledger.
    Revaluation of consumption valuates single-level consumption using the actual prices determined in the Actual Costing/Material Ledger application. This revaluation can either take place in the account where the original postings were made, or in a header account.
    The header account is determined using the transaction/event key COC.
    Del credere (DEL)
    Transaction/event key for the payment/invoice list documents in Purchasing. The account key is needed in the calculation schema for payment/settlement processing to determine the associated revenue accounts.
    Small differences, Materials Management (DIF)
    This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.
    Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)
    These transactions are used only if Purchase Account Management is active in the company code.
    Note
    Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).
    Before you use this function, check whether you need to use it in your country.
    Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)
    These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.
    You can also enter your own transactions for delivery costs in condition types.
    External service (FRL)
    The transaction is used for goods and invoice receipts in connection with subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    External service, delivery costs (FRN)
    This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.
    If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.
    Offsetting entry for stock posting (GBB)
    Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:
    AUA: for order settlement
    AUF: for goods receipts for orders (without account assignment)
    and for order settlement if AUA is not maintained
    AUI: Subsequent adjustment of actual price from cost center directly
    to material (with account assignment)
    BSA: for initial entry of stock balances
    INV: for expenditure/income from inventory differences
    VAX: for goods issues for sales orders without
    account assignment object (the account is not a cost element)
    VAY: for goods issues for sales orders with
    account assignment object (account is a cost element)
    VBO: for consumption from stock of material provided to vendor
    VBR: for internal goods issues (for example, for cost center)
    VKA: for sales order account assignment
    (for example, for individual purchase order)
    VKP: for project account assignment (for example, for individual PO)
    VNG: for scrapping/destruction
    VQP: for sample withdrawals without account assignment
    VQY: for sample withdrawals with account assignment
    ZOB: for goods receipts without purchase orders (mvt type 501)
    ZOF: for goods receipts without production orders
    (mvt types 521 and 531)
    You can also define your own account groupings. If you intend to post goods issues for cost centers (mvt type 201) and goods issues for orders (mvt type 261) to separate consumption accounts, you can assign the account grouping ZZZ to movement type 201 and account grouping YYY to movement type 261.
    Caution
    If you use goods receipts without a purchase order in your system (movement type 501), you have to check to which accounts the account groupings are assigned ZOB
    If you expect invoices for the goods receipts, and these invoices can only be posted in Accounting, you can enter a clearing account (similar to a GR/IR clearing account though without open item management), which is cleared in Accounting when you post the vendor invoice.
    Note that the goods movement is valuated with the valuation price of the material if no external amount has been entered.
    As no account assignment has been entered in the standard system, the assigned account is not defined as a cost element. If you assign a cost element, you have to enter an account assignment via the field selection or maintain an automatic account assignment for the cost element.
    Account determination of valuated sales order stock and project stock
    Note that for valuated sales order stock and project stock (special stock E and Q) and for the transaction/event keys BSX and GBB, you must maintain an account determination to avoid receiving warning messages when entering data (purchase order or transfer posting) for valuated stock.
    During data entry, the system attempts to execute a provisional account determination for GBB for valuated stock. The system will only replace the provisional account determination for GBB with the correct account determination for the stock account (BSX), in the background, if you enter the data for valuated stock at a later point in time.
    Purchase order with account assignment (KBS)
    You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.
    Exchange Rate Differences Materials Management(AVR) (KDG)
    When you carry out a revaluation of single-level consumption in the material ledger for an alternative valuation run, the exchange rate difference accounts of the materials are credited with the exchange rate differences that are to be assigned to the consumption.
    Exchange rate differences in the case of open items (KDM)
    Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.
    Differences due to exchange rate rounding, Materials Management (KDR)
    An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.
    Exchange Rate Differences from Lower Levels (KDV)
    In multi-level periodic settlement in the material ledger, some of the exchange rate differences that have been posted during the period in respect of the raw materials, semifinished products and cost centers performing the activity used in the manufacture of a semifinished or finished product are debited or credited to that semifinished or finished product.
    Consignment liabilities (KON)
    Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.
    Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:
    None for consignment liabilities
    PIP for pipeline liabilities
    Offsetting entry for price differences in cost object hierarchies (KTR)
    The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.
    Accruals and deferrals account (material ledger) (LKW)
    If the process of material price determination in the material ledger is not accompanied by revaluation of closing stock, the price and exchange rate differences that should actually be applied to the stock value are contra-posted to accounts with the transaction/event key LKW.
    If, on the other hand, price determination in the material ledger is accompanied by revaluation of the closing stock, the price and exchange rate
    differences are posted to the stock account (i.e. the stock is revalued).
    Price Difference from Exploded WIP (Lar.) (PRA)
    If you use the WIP revaluation of the material ledger, the price variances of the exploded WIP stock of an activity type or a business process are posted to the price differences account with transaction/event key PRA.
    Differences (AVR Price) (PRC)
    In the alternative valuation run in the material ledger, some of the variances that accrue interest in the cost centers, are transfer posted to the semifinished or finished product.
    Price differences (PRD)
    Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).
    Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.
    Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:
    None for goods and invoice receipts against purchase orders
    PRF for goods receipts against production orders and
    order settlement
    PRA for goods issues and other movements
    PRU for transfer postings (price differences in the case
    Price Differences (Material Ledger, AVR) (PRG)
    When you carry out a revaluation of single-level consumption in the material ledger during the alternative valuation run, the price difference accounts of the materials are credited with the price differences that are to be assigned to the consumption.
    Price differences in cost object hierarchies (PRK)
    In cost object hierarchies, price differences occur both for the assigned materials with standard price and for the accounts of the cost object hierarchy. In the course of settlement for cost object hierarchies after settlement via material account determination, the price differences are posted via the transaction PRK.
    Price Difference from Exploded WIP (Mat.) (PRM)
    If you use the WIP revaluation of the material ledger, the price and exchange rate differences of the exploded WIP stock of a material are posted to the price difference account with transaction/event key PRM.
    Price differences, product cost collector (PRP)
    During settlement accounting with regard to a product cost collector in repetitive manufacturing, price differences are posted with the transaction PRP in the case of the valuated sales order stock.
    This transaction is currently used in the following instances only:
    - Production cost collector in Release 4.0
    - Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
    Offsetting entry: price differences, product cost collector (PRQ)
    The offsetting (contra) entry to price difference postings (transaction PRP) in the course of settlement accounting with respect to a product cost collector in repetitive manufacturing in the case of the valuated sales order stock is carried out via transaction PRQ.
    This transaction is currently used in the following instances only:
    - Production cost collector in Release 4.0
    - Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)
    Price Differences from Lower Levels (PRV)
    In multi-level periodic settlement in the material ledger, some of the price differences posted during the period in respect of the raw materials, semifinished products, and cost centers performing the activity used in a semifinished or finished product, are transfer posted to that semifinished or finished product.
    Price differences for material ledger (PRY)
    In the course of settlement in the material ledger, price differences from the material ledger are posted with the transaction PRY.
    Expense and revenue from revaluation (retroactive pricing, RAP)
    This transaction/event key is used in Invoice Verification within the framework of the revaluation of goods and services supplied for which settlement has already taken place. Any difference amounts determined are posted to the accounts assigned to the transaction/event key RAP (retroactive pricing) as expense or revenue.
    At the time of the revaluation, the amounts determined or portions thereof) are posted neither to material stock accounts nor to price difference accounts. The full amount is always posted to the "Expense from Revaluation" or "Revenue from Revaluation" account. The offsetting (contra) entry is made to the relevant vendor account.
    Invoice reductions in Logistics Invoice Verification (RKA)
    This transaction/event key is used in Logistics Invoice Verification for the interim posting of price differences in the case of invoice reductions.
    If a vendor invoice is reduced, two accounting documents are automatically created for the invoice document. With the first accounting document, the amount invoiced is posted in the vendor line. An additional line is generated on the invoice reduction account to partially offset this amount. With the second accounting document, the invoice reduction is posted in the form of a credit memo from the vendor. The offsetting entry to the vendor line is the invoice reduction account. Hence the invoice reduction account is always balanced off by two accounting documents within one transaction.
    Provision for delivery costs (RUE)
    Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.
    Taxes in case of transfer posting GI/GR (TXO)
    This transaction/event key is only relevant to Brazil (nota fiscal).
    Revenue/expense from revaluation (UMB)
    This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).
    Expenditure/income from revaluation (UMD)
    This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.
    Unplanned delivery costs (UPF)
    Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.
    Input tax, Purchasing (VST)
    Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.
    Inflation posting (WGB)
    Transaction/event key that posts inflation postings to a different account, within the handling of inflation process for the period-end closing.
    Goods issue, revaluation (inflation) (WGI)
    This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.
    Goods receipt, revaluation (inflation) (WGR)
    This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.
    WIP from Price Differences (Internal Activity) (WPA)
    When you use the WIP revaluation of the material ledger, the price variances from the actual price calculation that are to be assigned to the WIP stock, an activity type or a business process are posted to the WIP account for activities.
    WIP from Price Differences (Material) (WPM)
    When you use the WIP revaluation of the material ledger, the price and exchange rate differences that are to be assigned to the WIP stock of a material are posted to the WIP account for material.
    GR/IR clearing (WRX)
    Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentation MM Material Valuation).
    Caution
    You must set the Balances in local currency only indicator for the GR/IR clearing account  to enable the open items to be cleared. For more on this topic, see the field documentation.
    GR/IR clearing for material ledger (WRY)
    This transaction/event key is not used from Release 4.0 onwards.
    Prior to 4.0, it was used for postings to the GR/IR clearing account if the material ledger was active. As of Release 4.0, the transaction is no longer necessary, since postings to the GR/IR account in parallel currencies are possible.
    Customers who used the transaction WRY prior to Release 4.0 must make a transfer posting from the

  • Roll out project

    Dear Friends,
       As a MM consultant what are the points to be consider during roll out project pls explain in points wise points must be rewarded.
      Regards
        Amin

    Dear friend,
    i will give the essance, upto my knowledge..if anything wrong please correct.
    Roll -out Project:
    Extending the business functionality from corporate to its branch office.Example: You have main office in German and they implemented SAP.Also they have branch in India and want to implement in India.When implementing SAP in India office( having same company in corporate level and assigning a company code for India to the same company), you can say it's a roll out project.
    Roll out example
    IF client is on SAP and runing SAP
    now he purchases new p-lant or set up new plant
    then going on to sap for this new plant is roll out
    IF client is on ECC5 and he want to go to laterast ecc6 or 7
    then this project for ecc5 to ecc 6 is call upgrade
    or conversion for non unicode to unicode client its also cale upgrade project
    So roll out project means you have to copy what are all the things in the old plant configuration, that things you have to copy that in new plant code..
    1.Company code is already maintained
    2.give plant code
    3.give storage location (how many storage location in new plant)
    4.purchase organization for this new plant
    5.Purchase group
    6.if any ware house module is there you have to give the bin, rack and related shipping point and delivery point,sales org, sales channel…….picking and packing….
    7.pr number ranges, document type and output type
    8.po number ranges and document type and output type for taking printout.
    9 gr document number ranges and out put type and document type(mb90)
    10. invoice screen config and output type…….(mr90)
    11.pricing procedure
    12.plant settings –both inventory and mrp related settings……..(u have to ask this information from your client)
    13.material master settings
    14.vendr number ranges and related settings in account group
    15.rfq and qutotation related settings…..
    16.if you have contract arrangement….then you have to give number ranges and document type and output type for taking printout
    17.if consignment is there…..same number ranges,document type and output type……
    18..if STO is there…..u have to give related document type and output type and number ranges………
    19.
    \if cin is ther,,,u have to define chapter id, delivery challan,TC,registers RG23A,RG23C,RG23D, and other 57fc and 5fAC sub-contracting challan.
    You have to confirm information related to account determination and account postings………
    If production planning module is there, u have to confirm,….mrp and procurement information…because requirement is generated from mrp…….
    thanks and regards,
    G.V.SHIVAKKUMAR
    9894150275

  • MFBF GR to Blocked stock with 103 MT Instead of 131

    Hi Guru's
    I want MFBF GR to blocked stock atomatic , with out using a Edit--> change detail settings-Blocked stock setting,
    i tried with assigning 103 Mov tye in Rep mfg profile for GR but it is giving Below error,
    I think it is FI ERROR
    So i think Could antbody Help for this issues
    Update control of movement type is incorrect (entry 103 X X _ F)
    Message no. M7226
    Diagnosis
    The system could not find entry 103 X X _ F in any of the movement type control tables.
    Procedure
    Cancel current processing.
    Contact your system administrator.
    Action to be taken by the system administrator
    Check in Customizing for Inventory Management under Copy, Change Movement Types whether the entry is contained in the Update control view for the movement type.
    If the entry is missing, proceed as follows:
    For standard movement types, this means that the given process is not supported using the present data combination. Do not create any entries without prior arrangement with your SAP consultant. Otherwise, incorrect postings may result.
    For customer-defined movement types (beginning with 9, X, Y, or Z), this may mean that they have not been fully defined. Delete the movement type and re-create it by copying a standard movement type.
    So could any body help in this regard with steps i will be greatefull to them.
    Reg
    Madhu

    Hi Madhu,
    You need to maintain settings in inventory management OMJJ transaction.
    For mvt type 103 set the allowed transactions MFBF and maintain update control /WM mvt types setting
    for 103 mvt and mvt indicator 'F'.
    Discuss with MM and FI members before these changes.
    Regards
    Venugopal

  • Need to make collection Query statement by sccm 2012 sp1 for Count of Licenses by License Status

    I want to make collection Query statement by sccm 2012 sp1 for all windows activated and all non-activated windows.
    Ahmed Sherif

    Have a look at the Software Licensing Product attribute classes when creating a Query - remember to choose
    System Ressource when creating the Query. You would have to enable this class to be collected during Hardware Inventory. Go to
    Client Settings -> Hardware Inventory ->
    Set Classes -> Select Software Licensing Product.
    This Class is part of the Asset Intelligence classes so you could enable it from there as well.
    Another way to accomplish is to use Compliance Settings to get this information.
    Create a Configuration item that query the Win32_WindowsProductActivation WMI Class, if you are using XP and the
    SoftwareLicensingProduct class for later os´s
    Add this Configuration Item to a Baseline ad deploy it to your Collections as needed.
    When the Baseline has been evaluated you can use this information to create query
    Machines reported as compliant is actived and machines reported as Non-Compliant is not activated.
    You can read about the Win32_WindowsProductActivation WMI Class here:
    http://msdn.microsoft.com/en-us/library/aa394520(v=vs.85).aspx
    and the SoftwareLicensingProduct here:
    http://msdn.microsoft.com/en-us/library/cc534596(v=vs.85).aspx

Maybe you are looking for

  • GoldenGate for DB

    Hi experts, we have a replication requirement between oracle to DB2 database,  please help on this, can we use data transformation like mapping and filtering in goldengate between oracle to DB2 databases?  and the actual requirment is, there is 5 tab

  • Could not release transport of an ABAP program

    Hello Expertise, I am facing the problems bellow while trying to transport a request. 1. Object REPT ZZSAPM07DR is inactive Message no. EU829 Diagnosis You tried to release a transport request, but object REPT ZZSAPM07DR is still in its inactive vers

  • Importing website from mobileme

    Hi I have recently reformatted my hard drive, and have have lost my site file in iweb. my page is still up on mobile me, is there a way to import my site so that i don't have to recreate it?

  • Nano 6G does not wake up from the sleep timer in the same audiobook/track

    My Nano 5G sleep timer will shutdown at the specified time and when I wake it, the Nano will be at the same track and position of my audiobook. However, my Nano 6G will wake up in a random song as if it shuffled after the shutdown. I test by setting

  • Increment a column by 1 each time the SP is called

    Hi folks, I'm trying to add 1 to the field Click each time this SP has run, not really sure how to implement this, code below; USE [TyreSanner] GO /****** Object: StoredProcedure [dbo].[CountClicks] Script Date: 12/18/2014 11:29:06 ******/ SET ANSI_N