Diff bet Budgetted cost & Planned Cost

Hi,
I created a project with Planned cost of Rs 1000 & then i budgtted amt of Rs 800 against it.But when in cj20n I generate any Purchase requisition against it System gives Error as Error in commitment items.Is always we hv to budget the same amt as in planned cost ?

Planned Costs are not binding but budgets are. You usually do planning first and then refer them to do you budgeting. Commitment check happens on Budget Values.
You can transfer the plan values into budget, you can do this either in CJ40 using Copy View option (copy plan costs) else use IMCCP3.
IMCCP3 is basically used for IM related planning and budgeting but it still works for copying the plan values as budgets.
Regards
Sreenivas

Similar Messages

  • Function Modules for Actual, Plan, Budget Cost over internal orders

    Dear All,
    I need a function module for getting the Actual, Plan, Budget Costs for the internal orders assigned.
    I want to fetch the cost related to internal order which is assigned to project C projects in PLM.

    hai tehre are no such funcion moduels
    u have to select from bpge and bpja tables
    and sum up them
    afzal

  • PM Budget Vs Planned Costs

    Hi Freinds,
    Is there a way to map Budget Vs Planned Costs for a PM Order? We know by Tcode:KO22 we can assign budget to a PM order against the actual costs.
    Anybody can throw some light on how to map the planned costs against the Budget.I have checked in SPRO on internal order where
    1. Budget profile is created for PM Order
    2. Budget profile is assigned to PM order types.
    So other than the above i couldnt get anything more to map the planned costs.
    This is quite urgent. Please throw some light on this
    Regards,
    Selva

    Some additional information:
    - after creating another PR with a different cost element, the costs are still not visible
    - I'm purchasing a text material (no number) and i'm purchasing a service without a service master.
    no idea if this has to do with it, but maybe it will help you

  • Marketing planning and budgetting(costing)

    Hello CRM Experts,
    My client wants to implement marketing planning and budgetting (costing). They do not want to use SAP Project System.**
    *.How campaign can be replicated in SAP ECC and assigned to WBS element. Can you please provide your imput as early as possible.*
    Thank you very much in advance
    Eliz

    hi,  guy
    to achieve this, you need to implement the BPS in BW, and make the BPS and CRM integration.
    In standard, CRM Marketing is integrated with BPS,  you can login the CRM and open the BPS windows in Marketing object screen, fill your cost plan or trade plan or sale plan.
    For WBS elment, you need to activate the configuration in PS mode and middleware between CRM and ERP.
    If you don't need to use PS, maybe you can use Claim in CRM to manage the expense and cost in campaign.

  • How can I edit budgeted cost/unit in excel and then import into P6?

    I would like to edit resource assignements (budgeted cost/unit) month by month in an excel file, and then import it into P6. Is this possible?
    It seems that the resource assignments month by month cannot be exported to an excel file. Is there anyone who can help me find a solution to this problem?
    Thanks a lot.
    By the way, I foud I can use the reporting function to get the excel file with month by month resource assignment information and can edit the values, but I cannot then import the changes into P6.

    not sure if this helps at all, but..
    when you refer to importing units (or costs) by period, do you mean past financial period actual data or future bucket planning data ?
    if it's the former, you can select corresponding financial period fields (period actual units and/or cost) for export to excell. unfortunately not sure why they are marked (*) which means they cannot be modified and reimported just as easily.
    an update of the same fields in the P6 database can be performed through P6 Timesheets (or similar solutions) through SDK (and possibly API or Webservices).
    if it's the latter, i don't see how *"future bucket planning" or any other non-linear distribution* (which can be a bit too much and quite time consuming in p6), can be made easier in excell.
    i think predefined non-linear resource curves are a good compromise, but if that doesn't suit your needs, you can define *"custom resource curves"* of your own for resource assignments using the resource usage spreadsheet.
    you would need to enter values for budgeted units for several future intervals (depending on the timescale)
    e.g. for months 1 to 4, you manually set budgeted units to 1, 0, 2 and 4h respectively, resulting in a total of budgeted units for the assignment of 7h.
    if you then modify the 7h to 70h, the sistem will adjust the period values proportionally to the initial values, resulting 10, 0, 20 and 40 h respectively.
    best of luck

  • Cost Center Budget-Cost element wise

    Dear SAP Gurus,
    My client needs to create cost center budgets cost element wise. For e.g. Salary paid (code 430000) in Development Cost center (code 9901).
    We now use KPZ2 to create cost center budgets and KP06 for cost element planning. Kindly guide.
    Regards,
    Siva

    Hi Ramesh,
    Thank you for the reply. I did suggest them to use KP06 but they require some sort of validation when posting an expense (cost element) to and cost center.
    For e.g. If the travel budget for Marketing cost center is $1000, they need the system to prevent posting once that amount is exceeded.
    Any help in this regard would be appreciated.
    Regards,
    Siva

  • What Is The Difference Between Budget Cost And Regular Cost For Resources?

    What's the difference betwee budget cost and regular cost for resources?
    Here is the explanation which I didn't understand from the book;
    In planning your departmental retreat, suppose you
    have specific budget targets
    for certain cost categories, $2,500
    for travel expenses, $500 for printing,
    and $1,000 for conference room rentals. Using Project’s budget resource
    feature, you can define your budget
    for different categories
    of items. You can then group your resources to
    com-pare your budgeted
    costs to your planned costs. This way, you
    can view your travel budget
    of $2,500 side by side with your planned
    costs of, say, $3,700,
    and immedi- ately see that your next
    goal is to find a way to trim those travel
    costs.

    Hi,
    You have to differenciate the proejct budget from the project cost:
    The project budget is the amount of money which has been allocated to your project by the executive board based on the estimation you provided. This is not meant to be changed unless you go through a change request process, justifying why you need to change
    (increase) the budget, meaning asking more money. Consequently it will not be related in MS Project with the tasks, assignments. It is entered on the project summary and can be meanly used in portfolio reports where you can consolidate yours budgets (you can
    have several different budgets) among a set of projects.
    The project cost is something which lives, changes along the project lifecycle. It is meant to be updated on a weekly or biweekly basis from the team members tasks updates approved by the project manager. Then the PM updates the remaining work thus the project
    cost.
    Hope this helps,
    Guillaume Rouyre, MBA, MVP, P-Seller |
    You say that the budget cost is total money which committee gave you for the project.
    But the book refer budget cost for every resource. I don't understand that.
    " In planning your departmental retreat, suppose you
    have specific budget targets
    for certain cost categories, $2,500
    for travel expenses, $500 for printing,
    and $1,000 for conference room rentals. Using Project’s budget resource
    feature, you can define your budget
    for different categories
    of items. You can then group your resources to
    com-pare your budgeted
    costs to your planned costs. This way, you
    can view your travel budget
    of $2,500 side by side with your planned
    costs of, say, $3,700,
    and immedi- ately see that your next
    goal is to find a way to trim those travel
    costs. "
    For example here travel budget cost is 2500 whereas planned cost is 3700. Planned cost of travel expense is created by the project manager. Who does define travel budget cost?
    Let's say an employee's cost is 20 dollars per hour and I write it on the project. So how much is this employee's budget cost, Who does define it, From whom do I learn that data?

  • How to show budget cost in the PPR screen?

    Hi all,
    I define budget cost of project already but in PPR screen It cannot show this value. It show only actual cost. Please advice me to show this value.
    Thank you.

    Only baselined budget values shown in the Project Performance Page.
    Also Run the Project Performance Summary Programs.
    Govind
    Edited by: GovindVenu on Jan 20, 2012 1:34 AM

  • Problem with loading budgeted cost in P6.7

    Dear All,
    I am using P6 ver 7.
    When I add a new resourse to load budgeted cost, already loaded resourse budgeted cost become zero.
    Help me please

    Hello,
    Are you adding the resource to a single activity? Or are you adding the resource to multiple activities through Excel? You may need to play around with the At Completion Cost to achieve your desired result.
    Hope this helps!

  • When Budget Cost Resources is assigned Project Summary Progress is Disabled

    When i create a Budget Cost Resource > assigned this resource to the project summary task > input the value, the "Summary Progress" indicator Bar on the Gantt chart, in project center for example, disappears. I remove the budget resource
    and the progress bar reappears. I have searched extensively and find no info. I can't believe this is intended.
    working with project professional client and server 2013 Dec 2013 CU and client hotfix applied 
    thanks in advance

    Answered on the LinkedIn Microsoft Project Users Group query.

  • Diff. bet Repetative  & Descrete mfg.

    hi...
    whats the diff. bet Repetative  & Descrete mfg.
    can i get some detailed ldifference

    please search in the forum..many threads with good explantiion available.
    These are three ways of production in a industries can happen.
    PP-discreet – required where there will be discrete orders passing through a work center, here the capacity planning plays major role. i.e. if you have a lath machine, many orders are going through this lathe m/c and schedule plays very important role w.r.t lath as well as the product as the product has to go through many work centre. Every time the product many not be same…can be different, but same work center can be used for many products.
    In PPPI- We are mainly concerned with quality parameters and Process management i.e control recipe is configured in this module. But the difference is the o/p is almost same…you will not change the product, but every step is very impartment to achieve the product quality. And it is entered by operator and approved by shift supervisor through control recipe function.
    REM- mainly to reduce the data input by person working in SAP and in this case we are bother about period end costing not the each order level costing as the process is repetitive and one order is sufficient for the wile life.

  • MIGRATION: Budget Billing Plans via Emigall

    Hello there!
    We are trying to migrate Budget Billing Plans via Emigall, and we don't really know how to do it... We have been checking all BBP_* Emigall Objects and, as far as we know, BBP_MULT object is the one we have to use...
    But we don't know if it is posible to migrate an opened BBP (meaning 'in process'). For example:
    bbp_number1. DUE_DATE=25.11.2009, invoiced, payment date=05.11.2009, clearing_doc=XXXXXXXXXXX1, ...
    bbp_number2. DUE_DATE=26.12.2009, invoiced, payment date=05.12.2009, clearing_doc=XXXXXXXXXXX2, ...
    bbp_number3. DUE_DATE=26.01.2010, invoiced, payment date=05.01.2010, clearing_doc=XXXXXXXXXXX3, ...
    bbp_number4. DUE_DATE=25.02.2010, invoiced, payment date=05.02.2010, clearing_doc=XXXXXXXXXXX4, ...
    bbp_number5. DUE_DATE=25.03.2010, invoiced, payment date=05.03.2010, clearing_doc=XXXXXXXXXXX5, ...
    -> MIGRATION <-
    bbp_number6. DUE_DATE=08.06.2010,not invoiced
    bbp_number7. DUE_DATE=08.06.2010,not invoiced
    ETC.
    There are a couple of important premises I want you to consider:
    -As this is a Company A to Company B migration, some data extractions can not be performed: Neither Bill Documents, nor Invoices will be migrated. All this data will be stored as PDF documents.
    -Only consumption data will be stored in the standard database.
    Will I be able to migrate this Budget Billing Plan without previously doing a regularization process (final bill, year-end bill) in the legacy system?
    Do I need to migrate billing and/or invoicing documents before migrating BBPs? (this would be impossible for me)
    What Emigall Object do I have to use?
    Every response will be welcome! Thanks in advance, best regards!

    Hi, and thank you very much for your answer.
    I understand what you mean but then, how do you do the final bill (regularization process)? At the end you know the amount the client has payed you, but you don´t know how much he payed on the legacy system, right?
    We are migrating them with the object BBP_MULT (and we try to migrate the whole plan, with 12 quotes), but we cannot migrate the "old" quotes, already payed in the legacy system. They appeared as "not payed", even if we inform the payment date, and the field "Clearing reason". Could you help us? Is it better to migrate them with the object you are using (BBP_EXT) instead of ours?
    Thank you!

  • Diff bet BDC in appln & present

    Gud morning guys,
    hav a gr8 day
    Coul any1 of  u tel me diff bet BDC in application layer and presentation layer...
    cheers
    sakthi

    Hi
    Hope it will help you.
    Reward if help.
    BATCH DATA COMMUNICATION
    About Data Transfer In R/3 System
    When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
    In the process of replacing current applications and transferring application data, two situations might occur:
    • The first is when application data to be replaced is transferred at once, and only once.
    • The second situation is to transfer data periodically from external systems to SAP and vice versa.
    • There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
    The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called “batch input” or “batch data communication”.
    1. SESSION METHOD
    2. CALL TRANSACTION
    3. DIRECT INPUT
    Advantages offered by BATCH INPUT method:
    1. Can process large data volumes in batch.
    2. Can be planned and submitted in the background.
    3. No manual interaction is required when data is transferred.
    4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
    To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a “data transfer” program must map the data from the external system into the data structure required by the SAP batch input program.
    The batch input program must build all of the input to execute the SAP transaction.
    Two main steps are required:
    • To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
    • To pass the table to SAP for processing.
    Prerequisite for Data Transfer Program
    Writing a Data Transfer Program involves following prerequisites:
    Analyzing data from local file
    Analyzing transaction
    Analyzing transaction involves following steps:
    • The transaction code, if you do not already know it.
    • Which fields require input i.e., mandatory.
    • Which fields can you allow to default to standard values.
    • The names, types, and lengths of the fields that are used by a transaction.
    • Screen number and Name of module pool program behind a particular transaction.
    To analyze a transaction::
    • Start the transaction by menu or by entering the transaction code in the command box.
    (You can determine the transaction name by choosing System – Status.)
    • Step through the transaction, entering the data will be required for processing your batch input data.
    • On each screen, note the program name and screen (dynpro) number.
    (dynpro = dyn + pro. Dyn = screen, pro = number)
    • Display these by choosing System – Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
    The technical info pop-up shows not only the field information but also the program and screen.
    • For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
    Note the following information:
    - The field name for batch input, which you’ll find in its own box.
    - The length and data type of the field. You can display this information by double clicking on the Data Element field.
    • Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
    Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
    In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
    You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
    Once you have program name, screen number, field name (screen field name), you can start writing.
    DATA TRANSFER program.
    Declaring internal table
    First Integral Table similar to structure like local file.
    Declaring internal table like BDCDATA
    The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
    The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
    This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
    • Create a BDCDATA structure
    • Write the structure out to a session or process it with CALL TRANSACTION USING; and then
    • Create a BDCDATA structure for the next transaction that is to be processed.
    Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
    The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
    • Data that is entered into screen fields.
    • Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
    The BDCDATA structure contains the following fields:
    • PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
    • DYNPRO: Screen Number. Set this field only in the first record for the screen.
    • DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to ‘ ‘ (blank) for all other records.)
    • FNAM: Field Name. The FNAM field is not case-sensitive.
    • FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
    Transferring data from local file to internal table
    Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
    Population of BDCDATA
    For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
    All these five initial steps are necessary for any type of BDC interface.
    DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
    First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
    SESSION METHOD
    About Session method
    In this method you transfer data from internal table to database table through sessions.
    In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
    Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
    When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
    Unless session is processed, the data is not transferred to database table.
    BDC_OPEN_GROUP
    You create the session through program by BDC_OPEN_GROUP function.
    Parameters to this function are:
    • User Name: User name
    • Group: Name of the session
    • Lock Date: The date on which you want to process the session.
    • Keep: This parameter is passed as ‘X’ when you want to retain session after
    processing it or ‘ ‘ to delete it after processing.
    BDC_INSERT
    This function creates the session & data is transferred to Session.
    Parameters to this function are:
    • Tcode: Transaction Name
    • Dynprotab: BDC Data
    BDC_CLOSE_GROUP
    This function closes the BDC Group. No Parameters.
    Some additional information for session processing
    When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
    However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
    If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
    CALL TRANSACTION
    About CALL TRANSACTION
    A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
    Call transaction <tcode> using <BDCTAB>
    Mode <A/N/E>
    Update <S/A>
    Messages into <MSGTAB>.
    Parameter – 1 is transaction code.
    Parameter – 2 is name of BDCTAB table.
    Parameter – 3 here you are specifying mode in which you execute transaction
    A is all screen mode. All the screen of transaction are displayed.
    N is no screen mode. No screen is displayed when you execute the transaction.
    E is error screen. Only those screens are displayed wherein you have error record.
    Parameter – 4 here you are specifying update type by which database table is updated.
    S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
    A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
    Parameter – 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
    1. Tcode: Transaction code
    2. Dyname: Batch point module name
    3. Dynumb: Batch input Dyn number
    4. Msgtyp: Batch input message type (A/E/W/I/S)
    5. Msgspra: Batch input Lang, id of message
    6. Msgid: Message id
    7. MsgvN: Message variables (N = 1 - 4)
    For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
    Steps for CALL TRANSACTION method
    1. Internal table for the data (structure similar to your local file)
    2. BDCTAB like BDCDATA
    3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
    4. Loop at itab.
    Populate BDCTAB table.
    Call transaction <tcode> using <BDCTAB>
    Mode <A/N/E>
    Update <S/A>.
    Refresh BDCTAB.
    Endloop.
    (To populate BDCTAB, You need to transfer each and every field)
    The major differences between Session method and Call transaction are as follows:
    SESSION METHOD CALL TRANSACTION
    1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
    2. No sy-subrc is returned. Sy-subrc is returned.
    3. Error log is created for error records. Errors need to be handled explicitly
    4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
    Error Handling in CALL TRANSACTION
    When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
    Steps for the error handling in CALL TRANSACTION
    1. Internal table for the data (structure similar to your local file)
    2. BDCTAB like BDCDATA
    3. Internal table BDCMSG like BDCMSGCOLL
    4. Internal table similar to Ist internal table
    (Third and fourth steps are for error handling)
    5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
    6. Loop at itab.
    Populate BDCTAB table.
    Call transaction <tr.code> using <Bdctab>
    Mode <A/N/E>
    Update <S/A>
    Messages <BDCMSG>.
    Perform check.
    Refresh BDCTAB.
    Endloop.
    7 Form check.
    IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
    Call function Format_message.
    (This function is called to store the message given by system and to display it along with record)
    Append itab2.
    Display the record and message.
    DIRECT INPUT
    About Direct Input
    In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
    You can start a Direct Input program in two ways;
    Start the program directly
    This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
    Starting the program via the DI administration transaction
    This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
    Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
    First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
    - Create variant
    - Define job
    - Start job
    - Restart job
    Common batch input errors
    - The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
    - The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
    - On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
    - The BDCDATA structure contains fields, which are longer than the actual definition.
    - Authorization problems.
    RECORDING A BATCH INPUT
    A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
    You can either use SHDB transaction for recording or
    SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
    And from here click recording.
    Enter name for the recording.
    (Dates are optional)
    Click recording.
    Enter transaction code.
    Enter.
    Click Save button.
    You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
    • Click Get Transaction.
    • Return to BI.
    • Click overview.
    • Position the cursor on the just recorded entry and click generate program.
    • Enter program name.
    • Click enter
    The program is generated for the particular transaction.
    BACKGROUND PROCESSING
    Need for Background processing
    When a large volume of data is involved, usually all batch inputs are done in background.
    The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
    Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
    There are several reasons to submit programs for background execution.
    • The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
    • You can use the system while your program is executing.
    This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
    The transaction for background processing is SM36.
    Or
    Tools ? Administration ? Jobs ? Define jobs
    Or
    System ? services ? Jobs
    Components of the background jobs
    A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
    • Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
    • Job class. Indicates the type of background processing priority assigned to the job.
    The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
    • Job steps. Parameters to be passed for this screen are as follows:
    Program name.
    Variant if it is report program
    Start criteria for the job: Option available for this are as follows:
    Immediate - allows you to start a job immediately.
    Date/Time - allows you to start a job at a specific name.
    After job - you can start a job after a particular job.
    After event - allows you to start a job after a particular event.
    At operation mode - allows you to start a job when the system switches to a particular operation mode.
    Defining Background jobs
    It is two step process: Firstly, you define the job and then release it.
    When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
    When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
    HANDLING OF POP UP SCREEN IN BDC
    Many times in transaction pop up screen appears and for this screen you don’t pass any record but some indication to system telling it to proceed further. For example: The following screen
    To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
    Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
    BDC_CURSOR is also used to place cursor on particular field.
    AN EXAMPLE WITH SESSION METHOD
    Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
    The transaction is TFBA (to change customer).
    A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
    Prerequisite to write this BDC interface as indicated earlier is:
    1. To find screen number
    2. To find screen field names, type of the field and length of the field.
    3. To find BDC_OKCODE for each screen
    4. Create flat file.
    Flat file can be created in your hard disk as follows:
    1 Vinod   Hyderabad
    2 Kavitha Secunderabad
    3 Kishore Hyderabad
    (Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
    To transfer this data to database table SCUSTOM following interface can be used.
    REPORT DEMO1.
    Following internal table is to upload flat file.
    DATA: BEGIN OF ITAB OCCURS 0,
    ID(10),
    NAME(25),
    CITY(25),
    END OF ITAB.
    *Following internal table BDCDATA is to pass date from internal table to session.
    DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
    Variables
    DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. “ This is for Hold Date
    To upload flat file to internal table.
    CALL FUNCTION UPLOAD
    EXPORTING
    FILE NAME = ‘C:\FF.TXT’
    FILE TYPE = ‘ASC”
    TABLES
    DATA_TAB = ITAB
    EXCEPTIONS
    CONVERSION_ERROR = 1
    INVALID_TABLE_WIDTH = 2
    INVALID_TYPE = 3
    NO_BATCH = 4
    UNKNOWN_ERROR = 5
    OTHERS = 6.
    If sy-subrc = 0.
    Calling Function to Create a Session
    CALL FUNCTION ‘BDC_OPEN_GROUP’
    EXPORTING
    CLIENT = SY-MANDT
    GROUP = ‘POTHURI’
    HOLDDATE = DATE1
    KEEP = ‘X’
    USER = SY-UNAME
    EXCEPTIONS
    CLIENT_INVALID = 1
    DESTINATION_INVALID = 2
    GROUP_INVALID = 3
    GROUP_IS_LOCKED = 4
    HOLDDATE_INVALID = 5
    INTERNAL_ERROR = 6
    QUEUE_ERROR = 7
    RUNNING = 8
    SYSTEM_LOCK_ERROR = 9
    USER_INVALID = 10
    OTHERS = 11.
    If sy-subrc = 0.
    *-- MAIN Logic--
    LOOP AT ITAB
    PERFORM GENERATE_DATA. “ Populating BDCDATA Table
    CALL FUNCTION ‘BDC_INSERT’
    EXPORTING
    TCODE = ‘TFBA’
    TABLES
    DYNPROTAB = BDCTAB
    EXCEPTIONS
    INTERNAL_ERROR = 1
    NOT_OPEN = 2
    QUEUE_ERROR = 3
    TCODE_INVALID = 4
    PRINTING_INVALID = 5
    POSTING_INVALID = 6
    OTHERS = 7.
    REFRESH BDCTAB
    ENDLOOP.
    Calling function to close the session
    CALL FUNCTION ‘BDC_CLOSE_GROUP’
    EXCEPTIONS
    NOT_OPEN = 1
    QUEUE_ERROR = 2
    OTHERS = 3.
    Endif.
    Endif.
    *& Form GENERATE_DATA
    Create BDC Data
    FORM GENERATE_DATA
    Passing information for 1st screen on BDCDATA
    BDCTAB-PROGRAM = ‘SAPMTFBA’.
    BDCTAX-DYNPRO = 100.
    BDCTAP-DYNBEGIN = ‘X’.
    APPEND BCDTAB.CLEAR BDCTAB.
    Passing field information to BDCDATA
    BDCTAB-FNAM = ‘SCUSTOM-ID’
    BDCTAB-FVAL = ITAB-ID.
    APPEND BDCTAB.CLEAR BDCTAB.
    Passing BDC_OKCODE to BDCDATA
    BDCTAB-FNAM = ‘BDC_OKCODE’.
    BDCTAB-FVAL = ‘/5’.
    APPEND BDCTAB.CLEAR BDCTAB.
    Passing screen information for next screen to BDCDATA
    BDCTAB-PROGRAM = ‘SAPMTFBA’.
    BDCTAB-DYNPRO = 200.
    BDCTAB-DYNBEGIN = ‘X’.
    APPEND BDCTAB.CLEAR BDCTAB.
    Passing screen information to BDCDATA
    BDCTAB-FNAM = ‘SCUSTOM-NAME’.
    BDCTAB-FVAL = ITAB-NAME.
    APPEND BDCTAB.CLEAR BDCTAB.
    Passing screen information to BDCDATA
    BDCTAB-FNAM = ‘SCUSTOM-CITY’.
    BDCTAB-FVAL = ITAB-CITY.
    APPEND BDCTAB.CLEAR BDCTAB.
    Passing BDC_OKCODE to BDCDATA
    BDCTAB-FNAM = ‘BDC_OKCODE’.
    BDCTAB-FVAL = ‘SAVE’.
    APPEND BDCTAB.CLEAR BDCTAB.
    ENDFORM. “GENERATE_DATA
    AN EXAMPLE WITH CALL TRANSACTION
    Same steps to be repeated for CALL TRANSACTION
    The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
    REPORT DEMO1.
    Follow above Code till MAIN Logic. Even the Subroutine should be copied
    LOOP AT ITAB
    PERFORM GENERATE_DATA, “Populating BDCDATA Table
    Call transaction ‘TFBA’ using BCDDATA Mode ‘A’ Update ‘S’.
    REFRESH BDCTAB
    ENDLOOP.

  • Creation of Budget Billing Plan for Countries with Tax Jurisdiction

    Hello Experts,
    When I create a budget billing plan for a company code with country Canada/USA and jursidiction TAXCAJ/TAXUSJ using transaction EA61, I get the message "Taxes with jurisdiction code not permitted with down payments"(Message no. >0194).  The long text for this message says "Delete your entry in the field for jurisdiction code"  Is any one aware where from this jurisdiction code should be deleted.
    Is it possible to create budget billing plan for countries with jurisdiction code at all ?
    Thanks in advance
    Venkat

    Hello Roopali,
    What I learnt in the process of exploring the functionality is that Payment PLan (BBP or AMB) is the budget billing method for countries with Tax Jurisdiction. Statistical, Partial & Payment Scheme only works when jurisdiction is not defined for tax procedure. Payment scheme is the recommend procedure for Eurpopean market
    Thanks for your clarification
    Best Regards
    Venkat

  • Calculation of Budget Billing Plan (Amounts)

    Hi,
    I have a case where I need to find out on what basis the new budget billing plan is calculated.
    I want to verify on basis of what consumption the calculation is taking place. Suppose the monthly BB Amounts are calculated on basis of a certain consumption, say 300m3 but it should ideally be 400m3. How can I verify this?
    The BB Plan got created while invoicing but where (event, FM, Sub Routine, exit) exactly is the BB Amount calculation taking place?
    Thanks in advance,
    Suresh Reddy

    Hi Suresh,
    During billing, system extrapolates demand up to the next scheduled meter reading date and billing is simulated for the budget billing period. This is how consumption gets calculated. So, you need to look out for next scheduled meter reading date and calculate expected meter reading using extrapolation procedure configured in system to know consumption considered.
    Hope this helps.
    Regards,
    Avinash

Maybe you are looking for