Your SlideShare is downloading. ×
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Journals SAP BPC 7
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Journals SAP BPC 7

1,299

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,299
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
67
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SAP Business Planning and Consolidation for NetWeaver - JournalsApplies to:SAP Business Planning and Consolidation for NetWeaver 7.0. For more information, visit the EnterprisePerformance Management homepageSummaryThis white paper covers the basics of Journals, creating Journal, Posting values, Defining Security forJournals, Parameters that can be set for Journals, Tables used by Journals and Reporting. Also it explains ascenario where this can be used.Author): G.Vijaya KumarCompany: Infosys Technologies Limited,Created on: 22 February 2010Author Bio G.Vijaya Kumar is a Software Engineer in Infosys Technologies Limited worked in a Ramp Up project in SAP BPC NW for Infosys Technologies and currently working in EPM COE for Infosys Technologies Limited.He also have more than a year of experience in SAP BPC NW.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 1
  • 2. SAP Business Planning and Consolidation for NetWeaver - JournalsTable of Contents1. Objective ......................................................................................................................................................... 32. Journal Concepts ............................................................................................................................................ 3 2.1 Journal Architecture .................................................................................................................................. 3 2.2. Journal Template Creation using Journal Wizard .................................................................................... 3 2.3. Creating Journal Entry. ............................................................................................................................ 9 2.4. Posting, RePosting and UnPosting values using Journal Templates. ................................................... 11 2.5. Reopening Journal Templates ............................................................................................................... 11 2.6. Querying Journal Templates .................................................................................................................. 133. Journal Security ............................................................................................................................................ 15 3.1 Journal Task Profile ................................................................................................................................ 15 3.2 Journal Property ...................................................................................................................................... 154. Journal Parameters ...................................................................................................................................... 165. Journal Tables .............................................................................................................................................. 176. Journal Reporting ......................................................................................................................................... 187. Scenario ........................................................................................................................................................ 20Related Content ................................................................................................................................................ 22Disclaimer and Liability Notice .......................................................................................................................... 23SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 2
  • 3. SAP Business Planning and Consolidation for NetWeaver - Journals1. ObjectiveThis white paper covers the basics of Journals, creating Journal, Posting values, Defining Security forJournals, Parameters that can be set for Journals, Tables used by Journals and Reporting. I have furtherexplained the usage of Journal in BPC NW using a scenario wherein we need to add multiple comments orremarks for any single detailed line item.2. Journal ConceptsJournals are used to make any adjustments in the data keyed to the application. Functionally this is usedafter all the data are keyed using Input Sheets to the application. Usually Journals are used by managers;they will be checking the data entered by the owners and make adjustments if any.2.1 Journal ArchitectureJournal is used to update the values in the Application as Input Schedule. We use the Journal Entries whichis created by the administrator for updating the application. Administrator creates the standard template andJournal Entries for making Journal Postings.Unlike in input schedules, the system appends data, it does not replace it. The Values from the Journal issaved as it is without finding any delta value for writing as the data from Input Schedule does. One Detailed Line Item can have only one Data Input Schedule Obtain Cube Delta Journal One Detailed Line Item can have Multiple Data2.2. Journal Template Creation using Journal WizardJournal template is designed for each application and it is application specific. The person who has gotassigned to “JournalAdmin” task profile can create Journal template from Admin client.The end users use the Journal template created for making Journal entries. The Journal Template is createdusing Journal wizard.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 3
  • 4. SAP Business Planning and Consolidation for NetWeaver - JournalsThe journal template creation includes the following steps, 1. Selecting the header dimensionThe Header Items are like the page key values in the Input Schedule. For any application this should alwaysinclude Time, Category and Reporting Currency (If present in the application) dimensions. Any numberdimensions can be Header dimension. Steps in Journal Creation 2. Setting the header dimension orderThis is to set the sequence of the Header dimension that occurs in the Journal Entry. This can be done byselecting the dimension in the Header Dimension area and move Up or Down using the buttons available.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 4
  • 5. SAP Business Planning and Consolidation for NetWeaver - JournalsSAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 5
  • 6. SAP Business Planning and Consolidation for NetWeaver - Journals 3. Set detail Dimension orderThe dimensions other than header dimension are called as detailed dimension and there should be at leastone detailed dimension in the Journal. When setting the detail dimension order you can specify the maximumnumber of detailed rows in the Journal Entry.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 6
  • 7. SAP Business Planning and Consolidation for NetWeaver - Journals 4. Creating Additional Header itemsThe Additional header items are nothing but additional information about the Journal template. This is anoptional field which user can either select or leave before saving the Journal Entry. The maximum length ofthis is 128 bytes.Each Additional header Item can have a sub-item which the user will be selecting while working on thejournal template.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 7
  • 8. SAP Business Planning and Consolidation for NetWeaver - Journals 5. SummaryThe last step is Summary and it gives the details of all the information added while creating the JournalTemplate using the Journal wizard. Summary of the Journal Template CreatedCreating a new Journal Template deletes all the Journal entries and their audit trail saved before and not thevalues saved using them.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 8
  • 9. SAP Business Planning and Consolidation for NetWeaver - Journals2.3. Creating Journal Entry.Journal Entries can be created for any application only if the Journal templates are created in the Adminclient for the corresponding application.The person having Post Journal access can post the values only if the Journal Entries are created by theadministrator.Steps in creating the journal entry involves the following,  Select Enter a new journal from Journal Tasks, this will open a new Journal Entry with the format of the Journal Template.  Once the new Journal Entry is opened, the values for all dimensions are to be filled by Double clicking the cells corresponding to the dimension member values.Note: It is not possible to save a Journal Entry without Header and Detailed Dimension Member Values.  The Journal Entry is saved using the “Save Journal” task available in journal Options.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 9
  • 10. SAP Business Planning and Consolidation for NetWeaver - JournalsThe Journal Entry and its contents after saving is given below, Header Dimension Additional Journal Header Item Entry Status Detailed DimensionSAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 10
  • 11. SAP Business Planning and Consolidation for NetWeaver - Journals2.4. Posting, RePosting and UnPosting values using Journal Templates.The Journal postings are to enter the data updates to the application. Any user can do Posting only if theyare assigned to PostJournal task profile and there should be some Journal Entries saved to work. TheJournal when saved for the first time, the system generates a Journal ID which is used to identify the specificJournal template.The steps involved in Posting the Journal are,  Open the Journal Entry Template  Select all Detailed dimension member values  Save the Journal  Enter the debit and credit values  Post the JournalPosting of data using Journal template depends on the check box values. If the check box for Balanced ifchecked, the system checks both credit and debit are balanced or not.The Posting of Journal entry appends the data to the application and all the other details about the JournalEntry, User, Time stamp in the Journal table so that it can be used for reporting.Reposting is posting the values in the journal again to the system. It is like entering the values twice.UnPosting is again posting the values in the journal but with reversed sign. The status of the journal nowbecomes UnPosted and the system saves a read-only copy of the Journal entry to record the changes madeto the database.Note : It is not possible to enter Debit and Credit in a single Line item.2.5. Reopening Journal TemplatesReopening a Journal Template is like copying the values in the Journal Entry to some other Journal Entrybased on some translation Rules which needs to be maintained.The Reopening of any Journal template is possible only if the translation table is maintained. The translationtable has the following columns,  ACCTYPE : Type of account ( INC,EXP,AST,LEQ )  ACCOUNT_PROPERTY : List of accounts with the specified property.  S_[Detailed Dimension] : Source Dimension  D_[Detailed Dimension] : Destination Dimension  Sign : 1 ( Credit and Debit are in same position ) or -1 ( Credit and Debit are interchanged )Once the columns in the translation table are maintained we need to save the rule. We can add new rowsand also can delete existing rows using the button provided.After maintaining the Translation table, select Reopen Journals from Journal Options. The following windowguide us in reopening the Journal Entry form some dimension member values to other required dimensionmember values based on the translation rule maintained.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 11
  • 12. SAP Business Planning and Consolidation for NetWeaver - JournalsOnce the Reopening of the Journal Entry is done a new journal entry with the specified Translation rule issaved in the system with the Old Journal Entry ID as the actual Journal Entry ID and Description as%REOPEN #ID%.Note: Conditions for Reopening a Journal Entry, 1. The Journal Entry Status should be POSTED. 2. Journal Parameter JRN_REOPEN should be set to 1.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 12
  • 13. SAP Business Planning and Consolidation for NetWeaver - Journals2.6. Querying Journal TemplatesThe Query is used in filtering the Journal Entries saved based on our requirement. The Query can be builtbased on any parameter like Journal ID, Application, User etc,. Filter ParametersIt can also be filtered based on the various status of the Journal Entry. Journal StatusOnce we execute the query, based on the filtering criteria the system will fetch all the Journal Entries. Wecan select any number of Journal Entries and perform various operations available at the bottom.  Selecting the Journal Entries and pressing Post button posts all the values in the Journal Entries selected.  Copy to will copy the journal Data to some other journal as per the details selected.  When any Journal Entry is copied from some other Journal Entry the description is maintained as %COPYTO #ID%.  Delete will delete the selected Journal Entries.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 13
  • 14. SAP Business Planning and Consolidation for NetWeaver - Journals  Open will open all the selected Journal Entries. When multiple Journal Entries are opened, we can move from one Journal Entry to other using the next and Previous button in Journal tool bar. Also the Selection list shows the list of Journal Entries opened. Next / Previous List of Journal Entries OpenedThe Preview of the Journal Entries can be seen in the Querying window without opening the Journaltemplate by selecting the required Journal Entry and clicking the “<<” button at the top of the JournalManager Query. Preview of the selected Journal EntrySAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 14
  • 15. SAP Business Planning and Consolidation for NetWeaver - Journals3. Journal Security3.1 Journal Task ProfileThe Security in case of Input schedule is depends on the secured dimension member values, like based onthe access permission provided to the user in member access profile they will be able to work on any InputSheet for the dimensions which they have access. But here in Journals even if they have access to alldimensions, they can be restricted using the journal through the task profile assigned to them. Below are theavailable tasks for the Journal,The task profile needs to be created depending on the access to be provided to the user and needs to beassigned to the user. The access privileged in the different task s for Journal are,  AdminJournal : Have access to Create Journal Template and Delete the Journal table through Admin client.  CreateJournal : Have access to Create New Journal Entries.  PostJournal : Have access to Post values through the journal Entries.  ReviewJournal : Have access to open the existing Journal Entries and Review it.  UnpostJournal : Have access to unpost the Journal values entered.The task CreateJournal when given to the user without write access for any data region, denies the user increating any Journal Entries for that data region. These tasks when assigned to the users they will be able toperform the corresponding action as assigned to them.3.2 Journal PropertyAll the base level dimension members which the user has the access are accessible using the JournalEntries. The Journal provides another way of security by limiting the access to the dimension memberswhich needs to be accessed through the Journal. This is done through the dimension property ENABLEJRN.This property needs to be added to the dimension where you want the members to be limited and set thevalue for the members which need to be accessed through Journal as “Y” against this property. Repeat thisfor each dimension you want to limit, and process the dimensions.For Example, the user might be accessing around 3 different dimension members say India,US and UK butwe need the user to access only one dimension member say India through Journal. So what needs to bedone is add the Property ENABLEJRN in the corresponding dimension and set the value India member as Yacross this property.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 15
  • 16. SAP Business Planning and Consolidation for NetWeaver - Journals4. Journal ParametersThe Journal template is common for an application, i.e., one application can have only one standard Journaltemplate. So the conditions for the Journal can be defined in the application parameters specific to theJournals. The Application Parameters that are specific to Journal and their details are given below,Parameter Description Possible ValuesJRN_BALANCE Controls whether Journals are 1 or Y: Journals must balance when they are required to be Balanced. posted. Journal users can save an unbalanced journal, but may not post it. 0 or N: Journals can be balanced or unbalanced. Journal users can change this behavior. If they select Balanced, it works the same as option 1. 2: Journals users are prompted to save the journal as balanced, but are not required to do so.JRN_MAXCOUNT The maximum number of Any Number as per requirement. journal entries returned from a query in the Journal Manager.JRN_ALLOWPOST Locking data for journal The sequence number of the Approval changes only. status code (Work Status).JRN_POST_OVERWRITE Controls whether the system 1 or Y: The Journal ID is preserved. keeps the same journal ID when saving journals that were 0 or N: A new ID generates when the previously set to Posted status, unposted journal is saved. but changed to Unposted status.JRN_DESC_MODE Controls whether member IDs 1 or Y: Member descriptions are shown as or descriptions are shown in the row and column headings. Journal template 0 or N: Member IDs are shown as row and column headings.JRN_REOPEN Controls whether the Journal 1 or Y: Journal Template is allowed to Template is to be Reopened or reopen. not. 0 or N: Journal Template is Not allowed to reopen.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 16
  • 17. SAP Business Planning and Consolidation for NetWeaver - Journals5. Journal TablesThe information about Journal template and Journal Entries are saved in BI Tables. These tables are samefor all the Journals in different Applications and different Appsets. The tables that save the Journal templateand Entry details are,Table Name Content DescriptionUJJ_JRNTMPL_INFO Contains information like Appset ID, Application ID, Journal Template IDUJJ_TMPL_FLDS Contains information like Appset ID, Application ID, Journal Template ID, Sequence Number, Dimension Name, Generic IndicatorUJJ_JRNL Contains all the information of Journal Entry like, User details, Time, Journal ID, Dimension Member along with the information in UJJ_JRNTMPL_INFO table.UJJ_JRNL_ADITMS Contains the information about the additional header items in the Journal Templates. TABKEY stores the Additional Header item and MEMBER stores Sub item value.UJJ_ADDEDITEMS Contains the details about the Additional Header Items like the Header item name and their Parent Name along with the standard information like Appset ID, Application ID and Journal ID.UJJ_TRANS_MASTER Contains the Master data information of the Translation file created for Reopening, like Account Type, Property, Sign of translation along with the standard information about the Journal.UJJ_TRANS_DETAIL Contains the detailed information about, reopening template from any other template with the translation file created. The information found in this table are Source Dimension Member, Destination Dimension member, Dimension Name and Sequence number along with the standard information about the template.These tables can be cleared using the Clear journal Table option in the Admin client. Only the Journal adminhas the access to clear the table. When cleared all the details about the Journal entries will be lost, not thevalues posted by the Journals. They remain in the system even after journal entries are deleted.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 17
  • 18. SAP Business Planning and Consolidation for NetWeaver - Journals6. Journal ReportingJournal reports are web based reports and are generated based on the journal entries. These reports includethe audit trail of all Journal entries. The report can be fetched based on,  Journal ID  User  AccountThe Journal Report by Journal ID generates a report based on a single journal entry. The Report by Usergenerates the report based on the list of users who have worked on the journal entries by creating, postingand unposting. The Report by account generates a report based on the account selected.The Reports can be generated in either HTML format or as a Excel file.Report in HTML format is shown below,SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 18
  • 19. SAP Business Planning and Consolidation for NetWeaver - JournalsAlso reporting can be filtered to any type of Journal like Saved, Posted, UnPosted, Deleted or All.Note: Journal Reports can be viewed only by the administrators.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 19
  • 20. SAP Business Planning and Consolidation for NetWeaver - Journals7. ScenarioConsider a business case where we require for a single detailed line item we need to enter n different valuesand comments.This problem is easily addressed by Journals.For some particular account there might be debit and credit values from different clients. This is not possibleto maintain in Input Schedule. The same case is solved in journal as below, Same Dimension Member Comment Values sThe multiple values entered in the Journal across Debit and Credit are grouped together and the net value isavailable in the report for reporting.Also the Remark Column is used in adding different comment across the same line item.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 20
  • 21. SAP Business Planning and Consolidation for NetWeaver - Journals All the values entered in Journal comes as a single value in ReportSAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 21
  • 22. SAP Business Planning and Consolidation for NetWeaver - JournalsRelated Contenthttp://help.sap.com/saphelp_bpc70sp02/helpdata/en/66/ac5f7e0e174c848b0ecffe5a1d7730/frameset.htmHelp available in BPC - http://servername/OSOFT/Help/Admin/HelpStart.htmFor more information, visit the Enterprise Performance Management homepageSAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 22
  • 23. SAP Business Planning and Consolidation for NetWeaver - JournalsDisclaimer and Liability NoticeThis document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,and anyone using these methods does so at his/her own risk.SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com© 2009 SAP AG 23

×