Planner Profile

Hi Experts,
Please help me on this ;
We have defined a new planning profile ( T-Code : KP66 ) and assigned that to a new planning profile in SPRO following the path : SPRO -> controlling -> cost center -> accounting -> planning -> manual planning -> define user defined planner profiles.
We need to define the file description in the above step for upload of the file. my main difficulty is that where this description of file will be stored and where we have to write the same
Thanks ,
Dhruv Kumar Malhotra

Hi,
Refer to this link, it describes the procedure:
http://help.sap.com/saphelp_erp60_sp/helpdata/en/e9/254f2815b311d2a5610060087a7a87/frameset.htm
Regards,
Eli

Similar Messages

About planner profile report

hi all
do any one about (planner profile report) and (price activity variance report)
can any one explain me about these two reports.
Thanks and regards,
kiran.

Hi Venkat,
Check this Thread
Re: Creating Aging Report and Counting report
Please search the Forum, you will get lot of more information.
Thanks
CK

File Description in Planner Profile

Hello All
I am facing similar issue which few others have faced , linking File Description to Planner profile & using in upload file.
I have linked the planner profile Z-ALLXL , 'integrated excel' with file description COB_* (as I intend to create sepearet file for different Cost centres for example : COB_C1.TXT , COB_C2.TXT)
But when I enter COB_* in planner profile it say it does not exist.
Also when I go to KP06 and use excel load, I cant see file description COB_ * is not available for selection. The only thing available is 01_1P1_KSKA_EX_001ETG-KSKA
I have refered from links before somehow not able to get through this.
Also I want to know the 'excel' macro that is generated for profile can this be exactly used for load or we need to change somethings here.
Best Regards

Hi Vijay
I would personally suggest using an LSMW... This excel upload is always a pain.. Moreover, you have to prepare files for each month separately...
I always use LSMW.. I recorded it 4 yrs back in my 1st project and have been using it ever since... You can export-import it between systems in a txt file format
Regards
Ajay M

FAGLFLEXT not appearing in planner profile

Dear all,
I am trying to create a planner profile for profit center planning with new gl. I have created in golden client and transported to production. But when i check in production the totals table for the SAPFAGL profile in the totals table FAGLFLEXT not found.
regards
ranga

It doesn't help.
I have the same problem and table FAGLFLEXP is forbidden in maintenance of planner profile (transaction GLPLADM). Planner profile works correctly only with FAGLFLEXT table.
Any other idea ?

Planner profile SAPFAGL and Summary Table is FAGLFLEXT

Dear Friends,
I am not able to enter plan data (Version 1) for Planner profile SAPFAGL and Summary Table is FAGLFLEXT.
Whenever i try to enter plan data, got error message GLS0 is not available. Why..?
Is there way to enter plan data (version 1) in Summary Table is FAGLFLEXT.....? We are in ECC 6.0. Please help me. Thanks in Advance.
I will give more points for this solution.
VK.

Hi VK,
Please find the details.
You must/can start the selection with the following parameters:
1. Company Code (required entry field)
Enter the company code of the accruals account to be checked.
2. G/L Account (required entry field)
Enter the accruals account to be checked.
3. Posting Period/Year To (required entry fields)
Enter the period to be checked in posting periods.
4. Indicator: Only Not Cleared Documents (optional entry field)
If you set this indicator, only actions with an incomplete revenue recognitions (revenue postings and billing document postings) are taken into account, because only these postings are necessary for an explanation of the balance. However, to trace the balance, it may be necessary for the system to also display completed (cleared) revenue recognition processes. In this case, the indicator must not be set, which generally has a negative effect on runtime.
              Note: The periods in the SD tables are determined by the posting date in the VBREVE and VBREVR tables.
If the necessary selection parameters were set and the report is started, a split screen appears.
1. Upper part of the screen - Balances
              This is where different balances are displayed for each currency in the form of a calculation. The calculation consists of the following:
a) Balance from revenue recognitions
This balance is determined from the posted revenue lines in the VBREVE table. These are the revenue amounts that were recognized in the selected period according to SD.
b) - Balance from billing documents
This balance is determined from the posted, billing items in the VBREVR table that are relevant for revenue recognition. These are the revenue amounts that were deferred in the selected period according to SD.
c) - Balance from other postings
If not only the revenue recognition process (VF44/VF46/VF01/VF02/VFX3) but also other FI transactions such as FB01 posted to the selected accruals account, then these values are not known in SD (VBREVx tables). This appears to result in an inconsistency between SD and FI, but there really is no inconsistency at all.
                       The system now takes the balance from revenue recognitions, minus the balance from billing documents, and compares the result with the total balance in FI. If there is a difference, the other postings on the selected accruals account for the selected period in FI are read. The result is the 'Balance from other postings.' If this balance is now also subtracted from the previous result, the determined value must result in the total balance from FI.
d) Total balance
This is the balance of the accruals account for the selected period that was determined in FI. If you now take the balance of revenue recognitions, minus the balance of billing documents and minus the balance of other postings, then the result should reflect the total balance in FI. If this is not the case, this result must be analyzed further, since there is an inconsistency between FI and SD. Transactions VF47 and VF45 (among others) are available for further analysis.
2. Lower part of the screen - VBREVx rows (SD tables)
This is where SD detail data (VBREVx tables) concerning the selection at sales and distribution document item level is listed (the total in the 'Balance' column must equal the total balance in FI). If the totals are different, there are inconsistencies between FI and SD.
              The following values are displayed for the items:
a) Billed revenues
For the relevant document item, the revenue billed in the selected period is displayed, based on the billing items relevant for revenue recognition (this is the revenue that was posted to the selected accruals account). Data is retrieved using the reference line table (VBREVR).
b) Recognized revenues
For the relevant document item, the revenue recognized in the selected period is displayed, based on the VBREVE table (this is the revenue that was posted to the selected accruals account). Data is retrieved using the revenue line table (VBREVE).
c) Accrued total value
This is the revenue amount of the document item to be recognized at accruals account level. Data is retrieved using the control row table (VBREVK) in which the relevant accrued total value is updated.
d) Balance
This balance at document item level is calculated by subtracting the recognized revenues from the billed revenues.
3. In addition to the screen described above, you can also receive more detailed information. The functions for the displayed ALV buttons are as follows:
a) Billing documents (F5)
This is where the billing items that are relevant for the selected document item are displayed. A jump to the respective billing document is also possible.
b) Other FI documents (F6)
If balances exist from other postings, the accounting documents which resulted in these balances are displayed here. A jump to the respective accounting document is also possible.
c) Overview (F7)
This is where the revenue recognition data that is relevant for the selected document item is listed. This is done in Transaction VF45 - 'Revenue Recognition: Overview.'
Implementation
1. Use Transaction SE38 to create the following program:
                    Name.....: SDRRAV53
       Title....: Compare report for revenue recognition
                     Create without a top include.
                  Attributes
      Type.............: Executable program
      Status...........: SAP Standard Production Program
      Application......: Sales
       Development class: VFE
2. Use Transaction SE11 to create the following structures in the VFE development class:
a) Data type (structure): VBREVBSIS
Short text...........: Output Structure for SDRRAV53
Enhancement category.: can be enhanced (deep)
(from Release 4.70)
                       Component Component type Ref field Ref table
BUKRS      BUKRS
BELNR      BELNR_D
GJAHR      GJAHR
HKONT      HKONT
BUDAT      BUDAT
WAERS      WAERS
MONAT      MONAT
SHKZG      SHKZG
WRBTR      WRBTR          WAERS      VBREVBSIS
ZUONR      DZUONR
TCODE      TCODE
AWTYP      AWTYP
AWKEY      AWKEY
b) Data type (structure): VBREVDETAIL
Short text...........: Detailed Structure for SDRRAV53
Enhancement category.: can be enhanced (character-type or numeric)
(as of Release 4.70)
                       Component     Component type Ref field Ref table
VBELN        VBELN
POSNR        POSNR
WAERS        WAERS
VBREVR_WRBTR WRBTR          WAERS      VBREVDETAIL
VBREVE_WRBTR WRBTR          WAERS      VBREVDETAIL
VBREVK_WRBTR WRBTR          WAERS      VBREVDETAIL
VBREVK_BAL    WRBTR          WAERS      VBREVDETAIL
c) Data type (structure): VBREVSALDO
Short text...........: Balance Table for SDRRAV53
Enhancement category.: can be enhanced (character-type or numeric)
(as of Release 4.70)
                       Component     Component type Ref field Ref table
WAERS        WAERS
SALDO        WRBTR           WAERS      VBREVSALDO
ORDERSALDO    WRBTR          WAERS      VBREVSALDO
FAKTURASALDO WRBTR          WAERS      VBREVSALDO
RESTSALDO    WRBTR           WAERS      VBREVSALDO
d) Data type (structure): VBREVINVOICE
Short text...........: Billing Data for SDRRAV53
Enhancement category.: can be enhanced (character-type or numeric)
(as of Release 4.70)
                       Component Component type Ref field Ref table
VBELN      VBELN_VF
POSNR      POSNR
WAERS      WAERS
WRBTR      WRBTR          WAERS      VBREVINVOICE
3. Implement the source code attached at the end. Use the "Note Assistant" to do this.
4. Add the following text elements to the SDRRAV53 report:
a) Selection texts
                       Name     Text                        Dictionary Ref
P_BUKRS Company Code                'X'
P_HKONT G/L Account                'X'
P_OPEN   only Not Cleared Documents ' '
b) Text symbols
                       Sym Text                                  dLen mLen
D01 Total Bal                              11 40
D02 Balance from Revenue Recognitions_____ 35   40
D03 Balance from Billing Documents________ 33   40
D04 - Balance from Other Postings__        33 40
D05 _____________________________          29   40
D06 Curr                                    7    7
D07 Bals                                    6    6
D24 Bal                                    5   18
D25 Recognized Revenue                    18   30
D26 Accrued total value                    25 40
D27 Billed Revenues                        18 40
E01 Period                                  8    8
E02 Acct                                    5    5
E03 Control                                9    9
E04 Posting Period/Year                    20 20
E05 To                                      3    3
              Start Transaction SE38 or SE80. Under the menu option "Goto" you will find the menu option "Text elements." Here you can make the changes listed above.
5. Create the GUI statuses INVOICE and STANDARD.
a) Copy the STANDARD statuses from the SAPLSALV program and remove the following FCODES: &ALL, &SAL, &NFO, &NTE, &CRB, &CRE, &ABC, &CRL, &CRR, &XPA, &EB9, &RNT_PREV, &OMP, &XML.
b) Add the following functions to the STANDARD status in the new program:
                       FCODE DETA
                       F-key Function text      Icon name      Info text
F5    Billing documents ICON_OVERVIEW Billing documents
                       FCODE REST
                       F-key Function text       Icon name       Info text
F6     Other FI documents ICON_FINANCING Other FI documents
                       FCODE VF45
                       F-key Function text Icon name    Info text
F7    Overview       ICON_PERIOD Revenue recognition overview
6. Use Transaction SE93 to create the following transaction:
      Transaction code.: VF48 (Report transaction)
      Development class: VFE
      Transaction text.: Revenue recognition: Compare report
      Program..........: SDRRAV53
       Selection screen.: 1000
Classification
       'x' - Professional User Transaction
   GUI capability
      'x' - SAP GUI for HTML
      'x' - SAP GUI for Java
       'x' - SAP GUI for Windows
7. Save and activate the objects that you have created.
Header Data
Release Status: Released for Customer
Released on: 16.11.2005 15:44:32
Master Language: German
Priority: Correction with high priority
Category: Advance development
Primary Component: SD-BIL-RR Revenue Recognition
regards,
Srinivas Muthyala

Planner Profiles - CCA

Hi
we have just completed data migration for the ECC6 upgrade.
I have finally managed to activate Funds Management in IMG.
My problem is that when i execute transaction KP06(Change CElem/Activity Input Planning) in Solution Manager i get an error: "Fund Accounting active: layout 1-101 is unsuitable" message no.KAFF002
how do i correct this? your help will be greatly appreciated
Thank you in advance

Hi,
Using the planning layout you specify what contents appear in the header, rows, and columns (elements) of your planning screens depending on the specific management requirements made by cost center planning.
Check KP66 T.code.
Thanks,
Rau

Is there any function module that brings out profile planner

Hello experts,
Is there any function module that brings out profile planner (I want to set planner profile as u201CSAP800u201D. I am using 7KE1 transaction.
Example: I know, the FM - K_KOKRS_SET_BATCHINPUT will set the controlling area to 'CTIC' for the entire batch input process.
Thanks in advance.

look at these fms..
CACS_PROFILE_PARTNER_READ
CACS_PROFILE_SHOW

Amendment of the default Profile Planner CJR2/CJR4

Friends, good afternoon
Can I take a course in PS?
When I use the profile of the CJR2/CJR4 planner that comes as default is the standard, namely Spall and I can set another profile planner in the transaction or at KP04, correct?
I ask you, are set to come another profile as default (CJR2/CJR4) rather than the standard (SAPALL)?

Your requirement can be fulfilled as below.
Weather it is CJR2 / CJR4 if you wanted to make any planner profile defaulted for the user.
There are two options.
1. To make Temporary planner profile as default for user. (only comeing out of txn & not log off the SAP )
go to txn CJR2 / CJR4 >Settings menu> Set Planned profile-->in the pop up window inser planner profile which you want to make mandatory --> Enter.
now if you are coming out of CJR2 /CJR4 once again go to txn. you will find that your set planner profile will come as default. The same you can verify via Ctr +F4.
2. To make Permanent planner profile as default for user. ( Log off the SAP)
go to txn CJR2 / CJR4 >Settings menu> Set Planned profile-->in the pop up window inser planner profile which you want to make mandatory --> Ctr +save --> Enter.
In this case, if user will log of to SAP and again log in than your user profile will be which you have maintained permanently by clicking save button.
SAP gives you SAPALL as planner profile by defalut to all the users.
If you set the planner profile in one txn say CJR2 the same changes will get reflected for the CJR4.
Regards
Nitin

Cost Center & Cost Element Excel Planning Profile Error - KP06

Hi,
I have created a layout for cost center/cost element planning.after that i have created planner profile.but while saving the generic file,i am getting the below error and not able to save that.Kindly advice me.
A later upload is not possible with this layout
Message no. K9363
Diagnosis
The layout cannot be used for an upload. This can be caused by one of the following situations:
The layout does not contain a data field that is ready for input.
The layout has a lead column that only contains the text for the characteristic value and not the characteristic value itself
The layout contains formulas
The layout has a complex lead column and contains empty lines.
System response
If generic file names have already been created (that is, an upload is intended), the file description cannot be saved.
Procedure
If you want to use the layout for an upload, configure it accordingly.
If one of the last three situations is the case, the layout can only be used for manual planning and not for an upload. In this case, remove the generic file name.
Thanks
Supriya

Hi Supriya,
Can you please review the attached notes as they should fix the problem.
489867 KP06 and following: Setting up an Excel upload
319713 Error with Excel upload - possible causes
Regards,
Abhisek

Planning Profile 7KE1

Hi Experts,
While Planning Profit Center wise for P&L system asking Planning Profile getting Error, see the screen shot wht should i select where we have to maintain for the same, kindly help me.
Kind regards
Pranav Kr. Gupta
SAP FICO Consultant.

Hi Pranav,
Apologies cannot view your screenshot so giving you general information. If possible please upload the screenshot again.
The prerequisite for planning is to set the planner profile whether it is Cost Center Planning or Profit Center Planning.
You can copy the planner profile from the standard layouts available using T.code: KP34PC for Profit Center planning. In this the layouts are being assigned in the planner profile along with the assignment of Document Type.
Also, if you want to use the Excel upload feature, the same layout needs to be designed first and then an assignment is required in planner profile to use the excel upload functionality.
Regards

SAP FI and CO Certification syllabus_camparison

Hello,
Currently would like to persue a SAP FI and CO course.
I m totally unaware of the SAP FI & CO course contents.
I have Syllabus covered by Siemens and Syllabus covered by private trainer.
Syllabus given by Siemen doesn't contain anything related to CO.
can anybody compare both of them and tell me what are the topics which are not covered by the private trainer ?
Your kind assistance will able me to take precise decision.
Oblige the needful.
rgrds/Vinod.
Herewith copied both the sourses:
SIEMENS:
TERP01     SAP ERP: Intro     1.5 Hours
TERP02     SAP ERP: Intro to SAP NetWeaver     1 hour     Objectives     Identify the different components of SAP NetWeaver
TERP11     SAP ERP: Introduction to NetWeaver Business Intelligence               Explain the business process functions each NetWeaver component supports
     (BI)
TERP21     SAP ERP: Intro to Processes in FI     6 hours     Contents     Financial Accountingu2019s role in the business
                    Organizational levels used in Financial Accounting
                    Financial Accountingu2019s components:
                    General Ledger
                    Accounts Payable
                    Accounts Receivable
                    Fixed Asset Accounting
                    Preparation of financial statements
Following are the detailed contents of the above syllabus
TFIN50     FI- I     10 days     Classroom
               Contents     u2022 Organizational units, master data and documents for Financial Accounting: company code,
                    fiscal year, currencies, general ledger accounts, customer and vendor master records, profit
                    center, document control, postings, clearing open items, cash journal
                    u2022 Handling of payments, dunning, correspondence and closing operations in Financial
                    Accounting:
                    Automatic payment program with clearing of open items
                    Automatic dunning program for creating dunning notices and correspondence
                    Overview of month and year-end accounting processes in Financial Accounting
                    Balance sheet and P&L
                    Preparatory closing postings in sub ledgers and the general ledger
                    Technical organizational and documentary steps in individual closing
                    Closing Cockpit
                    Configuration of periodic closings in Financial Accounting
SMO01     Intro Solution Manager               This course is meant to familiarize you with the principles and terminology of the SAP Solution
                    Manager. You will be introduced to the benefits of using the SAP Solution Manager during the
                    implementation of your SAP solutions and during ongoing support and operations.
TFIN52     FI- II     10 days     Classroom
     (Inclusive of case study)          Contents     u2022 Organizational structures, master data, and business processes in Asset Accounting:
                    Chart of depreciation, depreciation area, asset classes, master data , asset transactions,
                    valuation, periodic processing, information system
                    Evaluation methods in Financial Accounting (Info system and ABAP reports of general ledger
                    accounting, accounts receivable accounting, and accounts payable accounting, report variants,
                    selection variables in variants, List Viewer, sample evaluations using the drilldown reporting
                    tool)
                    Special G/L transactions and document parking
                    Validations and substitutions in Financial Accounting
                    Archiving in Financial Accounting
                    u2022 Case study: implementation of a fictitious demo company using specific business processes,
                    configuration and mapping of the company structure, master data, and business processes in
                    the SAP system
                    u2022 Review and certification preparation
                    u2022 Certification examination for Certified Application Associate - Financial Accounting with SAP
                    ERP 6.04 on the content of the courses SAP125, TERP01, TERP02, TERP21, SM001, TFIN50,
                    TFIN52
Private Trainer:
SAP FICO Syllabus
Srl No     Topic     Points Covered
1     SAP Overview     Concept of client
OverviewSAP Architecture
2     Enterprise Structure     Define Company, Company code & Assign the same.
Maintain Fiscal Year Variant,
Posting Period Variant, Document Number Ranges, Document Type,
Posting Keys, Field Status Variants & Groups & Assignment of the same wherever
necessary.
3     Simple Chart of Accounts     Create a simple Chart of Accounts, Assign the same, Edit GL A/cu2019s, Enter Transactions, Post with
reference, Account Assignment Model, Recurring Document and Batch Processing, Document
Parking and Document Extract.
4     Period End Closing     Understand the Closing concept, Close the company created, view the Balance Sheet, Accounts,
carry forward balances to the next year, and view the Retained Earnings Account.
5     International COA     Create a company encompassing all features of the SAP standard company 0001, create a COA
in line with the INT COA, Assign as necessary, Edit Gl A/c Collectively, Enter Transactions, Post
with reference, Account Assignment Model, Recurring Document and Batch Processing,
Document Parking and Document Extract.
6     Cash Journal / Banking     Create GL A/c for Cash Journal, Document Types, Number Range Interval, Setup Cash Journal,
Business Transactions, and Posting.
7     Taxation     Understand the concept of a non-jurisdictional Tax Proceedure, Condition Type, Access
Sequence, Account Key, Tax Codes, Input / Output Tax, Calculation and Posting. Jurisdictional
Tax Proceedure will be configured independently by the student at this stage.
8     Accounts Receivable     Create Customer Master Records, raise invoices, receive incoming payment, assign and clear
open items, Down payment request, creation and clearing, Maintain Terms of Payment. Instalment Payment terms to be configured independently by the student.
9     Dunning     Define Dunning Area, Dunning Keys, Dunning Proceedure, Dunning Notices.
10     Interest     Define Interest Calculation Types, Number Ranges, Arrears Interest Calculation, Interest Run
and Posting. Balance interest to be configured independently.
11     Accounts Payable     Create Vendor Master Records, Input Tax, raise bills, create outgoing payments.
12     Std Witholding Tax     Understand the concept of WT, Basic Settings, Calculation and Postings.
Extended WT will be configured independently by the student.
13     House Banks
Define House Banks, Outgoing Payment Configuration, Number Ranges for Cheques, and Bank
Reconciliation. Automatic Payment Run to be configured independently.
14     Foreign Currency Translation     Understand the concept of foreign currency translations, enter exchange rates, valuate open
items at closing with reversals.
15     SD/MM definition,
assignment, and integration     Define Credit Control Area, Valuation Level, Plant, Location, Division, Sales Organisation,
Distribution Channel, Storage Location, Shipping Point and Assignment of the same. Define
Common Distribution Channel and Division. Check Enterprise Structure for Sales and
Distribution. Understand integration concepts, and assign GL A/cu2019s.
16     Create Material [FERT]     Create material, initial stock entry, check stock of material.
17     Pricing Proceedure     Understand the concept of pricing procedure, condition type, access sequence, account key,
procedure determination, and maintenance of condition records.
18     Sales Order & Billing     Create Sales Order, Outbound Delivery, Billing Document, Accounting Entries.
19     Asset Accounting     Understand Organisation Structure, Chart of Depreciation, Depreciation Areas, Asset Classes.
20     Controlling
Cost Element Accounting
Cost Center Accounting     Maintain Controlling Area, Assign the same and maintain number ranges
Create Default Cost Center, Primary Cost Element, Secondary Cost Element
Activate Cost Center Accounting in Controlling Area, Maintain Standard Hierarchy, Create Cost
Center Groups and Cost Centers, Select Planner Profile, Cost and Activity Input, Enter Plan and
Actual amounts, Generate Variances, Redistribution and Assessment of Primary and Secondary
Cost Elements across Cost Centers.
21     New GL Concept     Configuration logic.

check this link for one example co certification
http://www.sap.com/services/education/certification/certificationtest.epx?context=[[C_TFIN22_64|G]]|
Thanks,
Ram

Data is not uploding for the following code in bdc

DATA:   bdcdata LIKE bdcdata    OCCURS 0 WITH HEADER LINE.
*       messages of call transaction
DATA:   messtab LIKE bdcmsgcoll OCCURS 0 WITH HEADER LINE.
*       error session opened (' ' or 'X')
DATA:   e_group_opened.
*       message texts
TABLES: t100,
        cosp.
*** Generated data section with specific formatting - DO NOT CHANGE ***
DATA: BEGIN OF record OCCURS 0,
* data element: KPP_VALUE
        bdc00(032),                              "Cost Center
* data element:
        bdc01(032),                              "Cost Element
* data element:
        bdc02(032),                              "January
* data element:
        bdc03(032),                              "february
* data element:
        bdc04(032),                              "March
* data element:
        bdc05(032),                              "April
* data element:
        bdc06(032),                              "may
* data element:
        bdc07(032),                              "june
* data element:
        bdc08(032),                              "july
* data element:
        bdc09(032),                              "august
* data element:
        bdc10(032),                              "september
* data element:
        bdc11(032),                              "october
* data element:
        bdc12(032),                              "november
* data element:
        bdc13(032),                              "december
      END OF record.
*** End generated data section ***
DATA: g_file TYPE string,                        "Input file var for FM
      g_count(4) TYPE n VALUE 0000,              "Counter
      g_flag(1),                                 "Flag
      g_bdc01(11),
      g_bdc02(11),
      g_bdc03(11),
      g_bdc04(11),
      g_bdc05(11),
      g_bdc06(11),
      g_bdc07(11),
      g_bdc08(11),
      g_bdc09(11),
      g_bdc10(11),
      g_bdc11(11),
      g_bdc12(11),
      g_bdc13(11).
DATA: g_objnr LIKE cosp-objnr. "Object Number
DATA: g_record TYPE string,    "work area to read from app server
      g_tab TYPE string.       "tab variable to separate the columns
*   Selection Screen Variables
PARAMETERS ctumode LIKE ctu_params-dismode DEFAULT 'A' OBLIGATORY.
PARAMETERS: user(12) DEFAULT sy-uname OBLIGATORY.     "user for session in batch
PARAMETERS cupdate LIKE ctu_params-updmode DEFAULT 'L' OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-t01.
PARAMETERS: p_file(256) LOWER CASE OBLIGATORY,   "Input file
            p_ver(3) OBLIGATORY,                 "version
            p_gjahr(4) OBLIGATORY,               "Fiscal Year
            p_prof(8) OBLIGATORY,                "Planner Profile
            p_lines(4) OBLIGATORY,               "No. of Lines
            p_kokrs(4) OBLIGATORY.               "Controlling area
SELECTION-SCREEN END OF BLOCK b1.
*   Initialization
INITIALIZATION.
*Shiva-Change -01/03/2007 Costom Authorization check.
INITIALIZATION.
INCLUDE zauthocheck.
*End.
CLASS cl_abap_char_utilities DEFINITION LOAD.
g_tab = cl_abap_char_utilities=>horizontal_tab.
* Start of Selection
START-OF-SELECTION.
*Set the Controlling area
PERFORM bdc_dynpro USING 'SAPLSPO4'     '0300'.
PERFORM bdc_field USING 'SVALD-VALUE(001)' p_kokrs. "Contr.area
PERFORM bdc_transaction USING 'OKKS'.
*Set the planner profile
PERFORM bdc_dynpro USING 'SAPLKPP6'     '1007'.
PERFORM bdc_field USING 'RKPP6-PLPROF' p_prof. "Planner profile
PERFORM bdc_transaction USING 'KP04'.
*Number of lines
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = p_lines
    IMPORTING
      output = p_lines.
*For use in FM g_file should be of type string
   g_file = p_file.
*Open the app server file
PERFORM sub_get_data.
*read all data one by one
* DO.
*    READ DATASET p_file INTO g_record.
*    IF sy-subrc <> 0.
*      EXIT.
*    ENDIF.
**Split the record at tab
*    SPLIT g_record AT g_tab INTO
*     record-bdc00 record-bdc01 record-bdc02
*     record-bdc03 record-bdc04 record-bdc05
*     record-bdc06 record-bdc07 record-bdc08
*     record-bdc09 record-bdc10 record-bdc11
*     record-bdc12 record-bdc13.
*    IF sy-subrc = 0.
*      APPEND record.
*      CLEAR record.
*    ENDIF.
* ENDDO.
*For every new cost center, check whether there is already some plan data
*that is existing. If yes, delete them and replace with new plan data. Else,
*upload the new data.
LOOP AT record.
*Start of every new transaction
    AT NEW bdc00.
      READ TABLE record INDEX sy-tabix.
      CLEAR cosp.
      CONCATENATE 'KS' p_kokrs record-bdc00 INTO g_objnr.
      SELECT SINGLE * FROM cosp WHERE objnr = g_objnr AND
                                      gjahr = p_gjahr AND
                                      wrttp = '01' AND
                                      vrgng = 'RKP1'.
      IF sy-subrc = 0.
        PERFORM bdc_dynpro      USING 'SAPLKPP0' '1000'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'KPP0B-VALUE(03)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=CSUB'.
        PERFORM bdc_field       USING 'KPP0B-VALUE(01)'
                                      p_ver.
        PERFORM bdc_field       USING 'KPP0B-VALUE(02)'
                                      p_gjahr.
        PERFORM bdc_field       USING 'KPP0B-VALUE(03)'
                                      record-bdc00.
        PERFORM bdc_dynpro      USING 'SAPLKPP2' '0106'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'Z-BDC02(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=CMAL'.
        PERFORM bdc_dynpro      USING 'SAPLKPP2' '0106'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'Z-BDC02(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=CDEL'.
        PERFORM bdc_dynpro      USING 'SAPLSPO1' '0200'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=YES'.
        PERFORM bdc_dynpro      USING 'SAPLKPP2' '0106'.
        PERFORM bdc_field       USING 'BDC_CURSOR'
                                      'Z-BDC02(01)'.
        PERFORM bdc_field       USING 'BDC_OKCODE'
                                      '=CBUC'.
        PERFORM bdc_transaction USING 'KP06'.
      ENDIF.
*The line count should be set to 0001 first
      g_count = 0001.
      PERFORM bdc_dynpro      USING 'SAPLKPP0' '1000'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    'KPP0B-VALUE(03)'.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=CSUB'.
      PERFORM bdc_field       USING 'KPP1B-ONLY'
                                    'X'.
      PERFORM bdc_field       USING 'KPP0B-VALUE(01)'
                                    p_ver.
      PERFORM bdc_field       USING 'KPP0B-VALUE(02)'
                                    p_gjahr.
      PERFORM bdc_field       USING 'KPP0B-VALUE(03)'
                                    record-bdc00.
    ENDAT.
*End of every new transaction
*If the line count increases what was specified in sel screen, reset it to 1
    IF g_count > p_lines.
      g_count = 0001.
      g_flag = 'X'.
    ENDIF.
    CONCATENATE 'Z-BDC01(' g_count+2(2) ')' INTO g_bdc01.
    CONCATENATE 'Z-BDC02(' g_count+2(2) ')' INTO g_bdc02.
    CONCATENATE 'Z-BDC03(' g_count+2(2) ')' INTO g_bdc03.
    CONCATENATE 'Z-BDC04(' g_count+2(2) ')' INTO g_bdc04.
    CONCATENATE 'Z-BDC05(' g_count+2(2) ')' INTO g_bdc05.
    CONCATENATE 'Z-BDC06(' g_count+2(2) ')' INTO g_bdc06.
    CONCATENATE 'Z-BDC07(' g_count+2(2) ')' INTO g_bdc07.
    CONCATENATE 'Z-BDC08(' g_count+2(2) ')' INTO g_bdc08.
    CONCATENATE 'Z-BDC09(' g_count+2(2) ')' INTO g_bdc09.
    CONCATENATE 'Z-BDC10(' g_count+2(2) ')' INTO g_bdc10.
    CONCATENATE 'Z-BDC11(' g_count+2(2) ')' INTO g_bdc11.
    CONCATENATE 'Z-BDC12(' g_count+2(2) ')' INTO g_bdc12.
    CONCATENATE 'Z-BDC13(' g_count+2(2) ')' INTO g_bdc13.
*Trigger a new page when the limit reaches.
    IF g_flag = 'X'.
      PERFORM bdc_dynpro      USING 'SAPLKPP2' '0106'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    g_bdc01.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=CP+'.
      g_flag = space.
    ENDIF.
    PERFORM bdc_dynpro      USING 'SAPLKPP2' '0106'.
    PERFORM bdc_field       USING 'BDC_CURSOR'
                                    g_bdc01.
    PERFORM bdc_field       USING g_bdc01
                                  record-bdc01.
    PERFORM bdc_field       USING g_bdc02
                                  record-bdc02.
    PERFORM bdc_field       USING g_bdc03
                                  record-bdc03.
    PERFORM bdc_field       USING g_bdc04
                                  record-bdc04.
    PERFORM bdc_field       USING g_bdc05
                                  record-bdc05.
    PERFORM bdc_field       USING g_bdc06
                                  record-bdc06.
    PERFORM bdc_field       USING g_bdc07
                                  record-bdc07.
    PERFORM bdc_field       USING g_bdc08
                                  record-bdc08.
    PERFORM bdc_field       USING g_bdc09
                                  record-bdc09.
    PERFORM bdc_field       USING g_bdc10
                                  record-bdc10.
    PERFORM bdc_field       USING g_bdc11
                                  record-bdc11.
    PERFORM bdc_field       USING g_bdc12
                                  record-bdc12.
    PERFORM bdc_field       USING g_bdc13
                                  record-bdc13.
    g_count = g_count + 1.
*at end of all records of a transaction
    AT END OF bdc00.
      PERFORM bdc_dynpro      USING 'SAPLKPP2' '0106'.
      PERFORM bdc_field       USING 'BDC_CURSOR'
                                    g_bdc13.
      PERFORM bdc_field       USING 'BDC_OKCODE'
                                    '=CBUC'.
      SKIP.
      WRITE:/ 'Cost Center:', 15 record-bdc00.
      PERFORM bdc_transaction USING 'KP06'.
    ENDAT.
ENDLOOP.
*&      Form sub_get_data
*       text
* --> p1        text
* <-- p2        text
FORM sub_get_data .
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = g_file
      filetype                = 'ASC'
      has_field_separator     = 'X'
    TABLES
      data_tab                = record
    EXCEPTIONS
      file_open_error         = 1
      file_read_error         = 2
      no_batch                = 3
      gui_refuse_filetransfer = 4
      invalid_type            = 5
      no_authority            = 6
      unknown_error           = 7
      bad_data_format         = 8
      header_not_allowed      = 9
      separator_not_allowed   = 10
      header_too_long         = 11
      unknown_dp_error        = 12
      access_denied           = 13
      dp_out_of_memory        = 14
      disk_full               = 15
      dp_timeout              = 16
      OTHERS                  = 17.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM.                    " sub_get_data
*   open dataset                                                       *
*FORM open_dataset USING p_dataset.
* OPEN DATASET p_dataset
*               FOR INPUT IN TEXT MODE
*               ENCODING DEFAULT.
* IF sy-subrc <> 0.
*    WRITE: / text-e00, sy-subrc.
*    STOP.
* ENDIF.
*ENDFORM.                    "OPEN_DATASET
**   close dataset                                                      *
*FORM close_dataset USING p_dataset.
* CLOSE DATASET p_dataset.
*ENDFORM.                    "CLOSE_DATASET
*        Start new transaction according to parameters                 *
FORM bdc_transaction USING tcode.
DATA: l_mstring(480).
DATA: l_subrc LIKE sy-subrc.
* batch input session
* call transaction using
REFRESH messtab.
CALL TRANSACTION tcode USING bdcdata
                   MODE   ctumode
                   UPDATE cupdate
                   MESSAGES INTO messtab.
l_subrc = sy-subrc.
WRITE: / 'CALL_TRANSACTION',
           tcode,
           'returncode:'(i05),
           l_subrc,
           'RECORD:',
           sy-index.
LOOP AT messtab.
    SELECT SINGLE * FROM t100 WHERE sprsl = messtab-msgspra
                              AND   arbgb = messtab-msgid
                              AND   msgnr = messtab-msgnr.
    IF sy-subrc = 0.
      l_mstring = t100-text.
      IF l_mstring CS '&1'.
        REPLACE '&1' WITH messtab-msgv1 INTO l_mstring.
        REPLACE '&2' WITH messtab-msgv2 INTO l_mstring.
        REPLACE '&3' WITH messtab-msgv3 INTO l_mstring.
        REPLACE '&4' WITH messtab-msgv4 INTO l_mstring.
      ELSE.
        REPLACE '&' WITH messtab-msgv1 INTO l_mstring.
        REPLACE '&' WITH messtab-msgv2 INTO l_mstring.
        REPLACE '&' WITH messtab-msgv3 INTO l_mstring.
        REPLACE '&' WITH messtab-msgv4 INTO l_mstring.
      ENDIF.
      CONDENSE l_mstring.
      WRITE: / messtab-msgtyp, l_mstring(250).
    ELSE.
      WRITE: / messtab.
    ENDIF.
ENDLOOP.
SKIP.
REFRESH bdcdata.
ENDFORM.                    "BDC_TRANSACTION
*        Start new screen                                              *
FORM bdc_dynpro USING program dynpro.
CLEAR bdcdata.
bdcdata-program = program.
bdcdata-dynpro   = dynpro.
bdcdata-dynbegin = 'X'.
APPEND bdcdata.
ENDFORM.                    "BDC_DYNPRO
*        Insert field                                                  *
FORM bdc_field USING fnam fval.
* IF fval <> nodata.
CLEAR bdcdata.
bdcdata-fnam = fnam.
bdcdata-fval = fval.
APPEND bdcdata.
* ENDIF.
from the flat file its reading first record in to the tab strip but not the second record for the same costcenter

So your sparse upper level members are dynamically calculated?
I wonder if that is interacting with the calc order of the attribute dimension and not valuing the way you want.
The DBAG has lots of good stuff on attributes: http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_esb_dbag/dattrib.htm
You might want to think about making the upper level members in Function stored/never share and see if you get the result you're looking for. If Function is sparse, I would think long and hard about whether I really want those members to be dynamically calculated because of retrieval performance impact.
Regards,
Cameron Lackpour

Problem with long text

Hi folks,
iam uploading longtext in transaction KP06 in bdc programing using create_text.
now my problem is if i pass selection criteria
case 1:
Vertion : N0
fiscal year : 2007
planner profile: CCPLAN4
then the budeget plan data uploading successfully along with long text.
case2: Vertion : N1
in this case also everthing wrking fine
case3: Vertion : 001
in this case budgetplan data uploading sucessfully but longtext is not uploading,
i debbug the proragm , create_text also returning sy-subrc = 0. but if i check in KP06 the long text is not there.
data declaration
vertion : VERSN type C(3)
can u tell me the problem is in logic or with FM ?
note : i checked with save_text also.
regards
neeru

HI Naimesh,
the FM Create_text internally contains both FMs save_text and commit_text,
even i debug the FM in case of vertion N1, N0 and 001,
all the cases sy-subrc = 0.
code:
CLEAR G_OBJNR.
LOOP AT RECORD.
COST = RECORD-BDC01.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = COST
    IMPORTING
      output = COST.
    CONCATENATE 'KS' p_kokrs record-bdc00 INTO g_objnr.
        SELECT SINGLE * FROM COSP WHERE OBJNR = g_objnr
                          AND GJAHR = P_GJAHR
                          AND VERSN = p_ver
                          AND KSTAR = COST.
IF SY-SUBRC = 0.
      LEDNR = COSP-LEDNR.
      OBJNR = COSP-OBJNR.
      GJAHR = COSP-GJAHR.
      WRTTP = COSP-WRTTP.
      VERSN = COSP-VERSN.
      KSTAR = COSP-KSTAR.
      HRKFT = COSP-HRKFT.
      VRGNG = COSP-VRGNG.
      VBUND = COSP-VBUND.
      PARGB = COSP-PARGB.
      BEKNZ = COSP-BEKNZ.
      TWAER = COSP-TWAER.
CONCATENATE LEDNR OBJNR INTO OBJNR.
CONCATENATE OBJNR GJAHR INTO TNAME1 separated BY SPACE10.
CONCATENATE TNAME1 WRTTP VERSN INTO TNAME2.
CONCATENATE TNAME2 KSTAR INTO TNAME3 separated BY SPACE.
CONCATENATE TNAME3 VRGNG INTO TNAME4 separated BY SPACE4.
CONCATENATE TNAME4 BEKNZ INTO TNAME5 separated BY SPACE10.
CONCATENATE TNAME5 TWAER INTO TNAME.
I_THEAD-TDOBJECT = 'CCSS'.
I_THEAD-TDID = 'COSP'.
I_THEAD-TDNAME = TNAME.
I_THEAD-TDSPRAS = 'E'.
APPEND I_THEAD.
i_tline-tdformat = '*'.
I_TLINE-TDLINE = RECORD-LONGTEXT.
APPEND I_TLINE.
loop at i_thead.
CALL FUNCTION 'CREATE_TEXT'
EXPORTING
    FID               = I_THEAD-TDID
    FLANGUAGE         = I_THEAD-TDSPRAS
    FNAME             = I_THEAD-TDNAME
    FOBJECT           = I_THEAD-TDOBJECT
SAVE_DIRECT       = 'X'
FFORMAT           = '*'
TABLES
    FLINES            = i_tline
EXCEPTIONS
NO_INIT           = 1
NO_SAVE           = 2
OTHERS            = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDLOOP.
CLEAR I_TLINE.
REFRESH I_TLINE.
CLEAR I_THEAD.
REFRESH I_THEAD.
SELECT SINGLE * from cokp into itab WHERE OBJNR = g_objnr
                          AND GJAHR = P_GJAHR
                          AND VERSN = p_ver
                          AND KSTAR = COST.
if sy-subrc = 0.
   itab-TXFLG = 'X'.
   append itab.
   write:/ 'Text saved for', record-bdc00 , record-bdc01.
   else.
      write:/ 'Text saved for', record-bdc00 , record-bdc01.
      ENDIF.
ENDIF.
my program wrking fine but the long text is not visible for vertion 001.
regards
niru

Error message : SOFFICEINTEGRATION143

Hi
Iu2019m making my planning layout in T-Code u2013 KEPM when I execute the planning method, I received this error message: Error while opening document.
Can anybody help me to resolve this error? Please see the message:
Error while opening document
Message no. SOFFICEINTEGRATION143
Diagnosis
An error occurred in the desktop application while opening a document.
Procedure
Check first whether you can insert a document from this desktop application as an embedded object in another application. The necessary menu item is usually 'Insert --> Object'. The application then lists all of the OLE document types. Choose the type corresponding to the desktop applciation. If the insertion fails, the error is in the desktop application itself.
This error has various causes. Often, it is caused by activating certain add-ins. Sometimes, the desktop application is wrongly installed. The error should not recur once you have disabled any add-ins or reinstalled the desktop application.
Procedure for System Administration
If you cannot solve the problem as described above, enter a problem message. There are notes relating to how to generate the log file using the program SAPROFFICEINTEGRATIONTRACE.
Regards
Louie
PS. We upgrade our SAP gui to 7.2 version

Hi Louie,
The most errors occur because the Microsoft Excel template stored
in Transaction KP34 for the corresponding layout is incorrect.
You cannot avoid this in advance since you have formatting options
(which cannot be deactivated) in Excel that result in problems in case
of an inplace.
Please check the following steps.
For each planning with active Integrated Excel the system needs a
template Excel sheet ("Template"), which is filled with the current
data (in accordance with the specifications on the initial screen)
upon the call of the planning screen.
In the profile maintenance (Transaction KP34), you can save a
separate template for every layout, e.g. to store color changes.
This template is stored in the R/3 system. If no separate template
exists for the current layout, the system uses an empty standard
template which contains the macros necessary for planning "only".
Error message SOFFICEINTEGRATION143 indicates that a separate
incorrect template was saved. In the most cases users
removed or hid lines lines while setting-up the template in
Transaction KP34, or he even stored own macros.
To repair the incorrect template presumably makes no sense, however,
since there is a "link" between the layout and the template,
removing the layout and inserting it afterwards again into the
planner profile often does not even help to make the layout
accessible again.
Using the utility program KPP7UT03 you can delete existing
templates. Here, it is important that you make a restriction to the
layout in question on the initial screen, since otherwise the system
may delete several (or even all !) Thus you should make the
following specifications:
a) Planner profile,
b) Subclass (always 01),
c) Table name (Planning area -> F4 input help) and
d) Planning layout.
The profile item is only relevant if a layout has been entered more
than once in the same profile. The program has no test run.
Afterwards the empty standard template is used again for the
respective layout.
For more detailed analyses of the template used in each case you can
save this onto your own hard disk as follows:
a) Set a breakpoint in function module KPP_XL_TEMPLATE_GET_COPY.
b) Call up the planning transaction, go to the planning screen.
c) When the function module is reached, "empty" variable I_MODUS.
d) Set a breakpoint to success message K9353.
e) Continue processing (F8).
f) The system generates a dialog box on which you can specify the target location of the Excel file.
g) Continue processing (F8).
h) Cancel the transaction when you reach the breakpoint.
You can now examine the template . Especially for recurring problems you can access the
changes stored this way.
Also recommend to check note 499152.
I hope it helps.
Regards,
Fernando Evangelista

File Description Error while running GLPLUP

Hi,
We are trying to upload planning data using transaction GLPLUP . But its giving a File Decsription not maintained error even though we are able to see the same in F4 help. Any clue as to how to resolve the same.
Thanks
Nidhi Jain

Hi,
In order to use GLPLUP first of all a planning layout needs to be created which has the charateristics and key figures exactly matching with the excel file. For example Company code, GL Account and Profit Center as characteristics and amount in local currency as key figure.
This planning layout needs to be entered into a planner profile. Standard profile can be copied and then the totals table (for example FLGLFLEXT) where the planning figures are going to be uploaded is mentioned in the planner profile.
Before using the t-code GLPLUP the planner profile is entered. This way the system will know that the excel file format is the same as that in the planner profile entered. If the format does not match it will issue an error message.
Regards
Sharabh

Planner Profile

Similar Messages

Maybe you are looking for