Transport of Delta Initializations in SAP BPC 10

Hi All,
I have created "Delta Initialization" in Organize Delta Initialization in BPC Development system. While running the corresponding Data manager package for Delta loads, I have selected the Delta Initialization created and everything is working fine.
Now I need to transport the "Delta Initialization" created in Development system to other environments (For Example, Quality System). But I did not find the Delta Initialization created in Development system during transports. Is there any way I could select these objects (Delta Initialization) during transports?
Please help me in finding the solution for this issue.
Thanks & Regards,
Ramesh.

Hi,
This means that Package Links calling Delta Initialization also have to be recreated in every other environment ? There is still a lot a manual actions to do when transporting a BPC NW application ; integration with NW Transport System is still not complete...
Thanks & Regards,
Vincent

Similar Messages

Transport Control in SAP BPC 7.0 M

Hi,
We are an IT company with more than 250 reporting units. We intend to implement SAP BPC 7.0 M in our organisation to unify our forecating and reporting process across reporting units. I gather that there is no transport tool available in BPC to transport from development to quality to production. I am curious to know if SAP has provided a best practice for controlling changes to production. What is the best method to ensure that an administrator or a developer does not incorrectly make changes in the production system?
Also how do we convince our internal infra guys that changes have to be made directly in production? We have a central team for remote hosting all our systems and they have raised some following questions related to the security/disaster recovery aspects.
a. What is the backup and recovery procedure in case something happens to the production system.
b. Is there a best practice that I could refer to with respect to transports to convince them.
I am trying to prepare a document to convince them. I have got come inputs from sdn but I would really like an authoritative source to better understand this. Any answers/help would be highly appreciated!
Rgds
Shivram.

Hi Shivram,
for diaster recovery, you can just use the backup/restore functionality in BPC server manager. Where an admin can schedule it. Even you can use the SQL backup functionality, but if you use this you need to manually backup the fileshare folder.
Regarding Transports, yes when the project is already in production, it is a bit dangerous to use the backup/restore functionality as we will loss the production system data. So need to use the dev/QA system to develop and test it and later do the changes manually in production system. Before take a backup of production system, then you will be safe.
regards,
Sreedhar

Delta Initialization vs Delta Update

We're having some issues with performance when loading our GL cube. What I would like to do is perform many delta initializations, each delta inititialization containing one month/period.
My confusion is in the fact that the last time I attempted this, when I subsequently went to run my delta UPDATE the same selection criteria was automatically inserted into my delta update.
So for example my INIT may look like this;
REQUEST1: Selection = 001.2005
REQUEST2: Selection = 002.2005
etc........etc...
REQUEST12: Selection = 012.2005
Next the UPDATE info package seems to inherit the same criteria... doesn't this mean it will not update anything beyond that criteria??
I'm just wondering if it is possible to do an incremental initialization and still be able to enable delta updates for future periods?
Thanks!

Hi Patrick,
The delta update will load the data as per the selections made in the Init run. A delta requested after several initializations, contains the sum of all the successful initial selections as a selection condition. This selection condition can then no longer be changed for the delta.
Take a look here for more info:
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/content.htm
Hope this helps...

SAP BPC 7.5 - Loading Directly from r/3.

Hi,
anyone which has experience in loading directly from R/3 into SAP BPC ?
are there any starterkits for this ? Only I can find are IFRS, but there are of course many starterkits which can be purchased from 3rd part.
Pro/Cons using this direcly load process instead of having SAP BW in between as a datawarehouse ?
I would appreciate all input.
Thank you,
Joergen Dalby

Hi,
It is possible to have multiple BW/BI systems for one R3/ECC systems. In order for you to load data into both 3.5 and 7.0 systems, you need to difine BI 7.0 logical system in R3/ECC just like your BW 3.5 logical system in R3/ECC. In R3/ECC, the outbound queue (SMQ1) differentiates the deltas based on the logical system name that you have defined (3.5 and 7.0) in R3/ECC system. So, in RSA7 you will see same delta queue name twice but differentiated by logical system name. So you will not have problems loading deltas. Hope this will shed some light.
Regards,
Rao.

Enabling Journals in a Model in SAP BPC 10.0 MS

Hi,
Where does one enable journals functionality in SAP BPC 10.0 MS?
Here's the background:
I created a new Environment from EnvironmentShell
Worked on dimensions, member sheets etc. in the Consolidation Model
In the SAP Web Administration, Consolidation Monitor, I get the error Initialization Failed when clicking on the Journal item in the TreeView on the left. Clicking on the See Details, I get the error JOURNAL_NOT_ENABLED.
In the Planning and Consolidation Administration Client, I get a similar error when clicking on Define Journal Validation Rules or Define Journal Translation Rules. (Journal in not enabled in Consolidation)
I then thought I would be clever and modified the column 'Journal' in the table dbo.tblApp by putting a '1' there.
Refreshing the Planning and Consolidation Administration Client, I see that for the Consolidation Model, the Journals are specified as 'in use'. However, returning to the SAP Web Administration and clicking on the Journal option, the error I now get is 'Invalid object name dbo.jrnAddedItems', probably because my backdoor hack circumvented some code.
Where does one enable journals in a Model on the MS 10.0 platform? For the life of me, I can't find it. This despite much searching. Clearly I am missing something obvious.
Kind Regards
Nick

Hi Arnold,
Thanks. Yip, that's it. (I knew I was missing something remarkably obvious - it's just that I could not find it for some strange reason.)
Again, many thanks.
Kind Regards
Nick

Extraction, Flat File, Generic Data Source, Delta Initialization

Extraction, Flat File, Generic Data Source, Delta Initialization
I have couple of questions regarding data extraction.
1.     If you have Data Source a Flat File e.g. Excel file I know that you have to create Data Source at BW side. How do you upload updates, by selecting Delta Update when executing next Data Load? Do you ever u201Cconvertu201D this Excel file into Application Tables to become SAP Source 
2.     Can you please give me example of situation where you had to create Generic Data Source? What is difference between Time Stamp, Calend. Day and Numeric Pointer. Which one is most common to select?
3.     I read somewhere that Generic Data Source does not have Setup Table. I thought that you have to have Setup Table in order to load transaction Data otherwise you will lock the Application Tables. Where am I going wrong im my thinking please?
4.     What are steps in terms of IP before, under and after Delta Initialization. I belive that you can do two ways:
Full Update - Initialize Delta Process (without Data Transfer) u2013 Delta Update or
Initialize Delta Process (with Data Transfer) u2013 Delta Update
Am I right? What is most common method and why?
5.     If you want to add a filed in Data Source after 6 month using it, you want to do it without re-init Delta Queue. You add field in RSA6, then provide info for ABAP to populate new filed (info u2013 name of Data Source, Extract Structure, field added, name of Application Table which contains the field). How does it work now as there is no SetUp table it has been deleted after Initialisation? How does Delta Queue know that it is going to receive data which has been expanded by one field or it may does not need to know at all?
THANKSSSSSSSSSs

Hi,
1. If you have Data Source a Flat File e.g. Excel file I know that you have to create Data Source at BW side. How do you upload updates, by selecting Delta Update when executing next Data Load? Do you ever u201Cconvertu201D this Excel file into Application Tables to become SAP Source
Once you create Datasource for A flat file extraction then it is file source system specific hence you cont change to Application table source Data source
In info package you can change the source as application server instead of desktop no need to change the DS
2. Can you please give me example of situation where you had to create Generic Data Source? What is difference between Time Stamp, Calend. Day and Numeric Pointer. Which one is most common to select?
When we don't find any standard extractor then we can go for Generic(if i want information sales along with finance information in a data source then generally we dont get standard one hence we can go for generic DS)
Check the below link for More about generic DS .
http://wiki.sdn.sap.com/wiki/display/BI/Generic+Extraction
for Delta capturing you can use
Timestamp(if the table has time stamp filed so it can stamp the last changed record in that table hence it is easy to get delta based on the time stamp)
Calday- (If the table doesn't have the Timestamp filed then search for Calday where you can stamp the delta based on the date when documents are changed )
Numericpointer : If the table doesn't above both then we go for this option where you can the numeric value change stamp )
3. I read somewhere that Generic Data Source does not have Setup Table. I thought that you have to have Setup Table in order to load transaction Data otherwise you will lock the Application Tables. Where am I going wrong im my thinking please?
Generic datasource nothing but we extracting data directly from the database table without any interface between the application/systems
4. What are steps in terms of IP before, under and after Delta Initialization. I belive that you can do two ways:
Full Update - Initialize Delta Process (without Data Transfer) u2013 Delta Update or
Initialize Delta Process (with Data Transfer) u2013 Delta Update
Am I right? What is most common method and why?
Correct
5. If you want to add a filed in Data Source after 6 month using it, you want to do it without re-init Delta Queue. You add field in RSA6, then provide info for ABAP to populate new filed (info u2013 name of Data Source, Extract Structure, field added, name of Application Table which contains the field). How does it work now as there is no SetUp table it has been deleted after Initialisation? How does Delta Queue know that it is going to receive data which has been expanded by one field or it may does not need to know at all?
Once you add the new field to structure(DS) you will get the data as on date onwards not historical data hence what is the concept of setup table ( delta records come from the Delta Que not from the setup table )
If you want histaric data to new field then you need to setp table deletion ...etc...
Hope it is clear..
Regards,
Satya

When are init entries done in source system?And early delta initialization?

Hi Friends,
Q1) When are the init entries done in source system?
If INIT entries are done when I run INIT that means:
If my setup job finishes at 6AM and I run the INIT at 1 PM will I loose all data between 6AM and 1PM?
If INIT entries are done when I run setup table i.e. when setup table load finish then
If my setup job finishes at 6AM and I run the INIT at 1 PM...it will load data till 6AM
and after that data would bere there in Delta queue. So, this is ok...as no loss of data.
Q2) I have read on help.sap that "With early delta initialization, you have the option of writing the data into the
delta queue or into the delta tables for the application during the initialization request in the source
system. This means that you are able to execute the initialization of the delta process (the init request),
without having to stop the updating of data in the source system."
Does this mean when I run INIT at 1PM, no V1 updates will happen for that DS in Source System?
If Yes, that means I should always (when users are online) run INIT with early delta initialization
during times when users would be online?
Thanks!

Hello,
You will find the answers to the questions that you ask and the correct procedure to follow in the SAP note 602260.
Best Regards,
Des

Early delta initialization

Hello Gurus,
What are the scenarios we use Early Delta Init.
Is it available for Logistics datasources.
Full points to right answers.
Thanks in advance.

hi BW,
check this
http://help.sap.com/saphelp_nw2004s/helpdata/en/80/1a65dce07211d2acb80000e829fbfe/frameset.htm
Early Delta Initialization
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the updating of data in the source system. You can only execute an early delta initialization if the DataSource extractor called in the source system with this data request supports this.
Extractors that support early delta initialization were delivered with Plug-Ins as of Plug-In (-A) 2002.1.
You cannot run an initialization simulation together with an early delta initialization.
yes, it's available for logistics - oss note 505700, you can cross check the infopackage.
hope this helps.
505700-LBWE: New update methods as of PI 2002.1
g) Early delta initialization in the logistics extraction:
As of PI 2002.1 and BW Release 3.0B, you can use the early delta initialization to perform the delta initialization for selected DataSources.
Only the DataSources of applications 11, 12 and 13 support this procedure in the logistics extraction for PI 2002.1.
The early delta initialization is used to admit document postings in the OLTP system as early as possible during the initialization procedure. If an early delta initialization InfoPackage was started in BW, data may be written immediately to the delta queue of the central delta management.
When you use the "direct delta" update method in the logistics extraction, you do not have to wait for the successful conclusion of all delta Init requests in order to readmit document postings in the OLTP if you are using an early delta initialization.
When you use the "queued delta" update method, early delta initialization is essentially of no advantage because here, as with conventional initialization procedures, you can readmit document postings after successfully filling the setup tables, provided that you ensure that no data is transferred from the extraction queue to the delta queue, that is, an update collective run is not triggered until all of the delta init requests have been successfully posted.
Early Delta Initialization

NO Version Management in SAP BPC-is it in SAP BPC7.0 NW AND/OR SAP BPC70 MS

All,
As far as I know SAP BPC doest not have versions management. How you guys out there handle version management for SAP BPC. Do we have VM on SAP BPC 7.0 NW?
Why there is no VM in BPC. Come on convince me : - )
Thanks,
SK

Guys,
What is the verdict on Version Management being there in BPC? Can you (Saquib or others) give an example as to what Version Management functionality you might be looking for?
From the little I know, when you are doing software development through lifecycle (in SAP it would be called Transport strategy) management, you promote different changes in the target system and hence SAP has an implicit version management. I am assuming that BPC 7.0 NW version would have that automatically since it is promoted through transport strategy only. Are you referring to the same thing as version management or is it something else? But I also read somewhere that only appset is promoted through transport and not sure if each and every component is part of that.
Please enlighten with your insighs.
Thanks.

Need for locking system for delta initialization (BW-R3-LO)

Hello all,
Could someone please help me with the following,
Please be kind, don't get impatient for the lengthy post
1. Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
3. Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
    If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
             a). say, I do full load with end date and time (10pm 12-31-2007)
             b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
         If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
         If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
4. How this scenario differs to early delta initialization?
Your responses would be greatly appreciated
Thank you

Hello,
1
>
curious maven wrote:
> Do we need to lock the system (or posting-free the system) to do early delta initialization or not? If yes, please explain me how that work?
No,you don't need to lock the Source System which is the advantage of Early Delta Init.
With early delta initialization, you have the option of writing the data into the delta queue or into the delta tables for the application during the initialization request in the source system. This means that you are able to execute the initialization of the delta process (the init request), without having to stop the posting of data in the source system. The option of executing an early delta initialization is only available if the DataSource extractor called in the source system with this data request supports this.
[Business Information Warehouse 3.0 Overview Presentation|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9a0e9990-0201-0010-629b-dc2735cb9c81]
2
>
curious maven wrote:
> 2. Someone somewhere mentioned that early delta initialization is not preferable compared to normal delta initialization, even though early delta initialization is advantageous. Why is that so?
Early delta is not supported by all the extractors. See Lo Extraction
3
>
curious maven wrote:
Imagine, while scheduling Queued Delta Init or un-serialized V3 delta Init, if I choose certain end date and time (say, 10pm, 12-31-2007) for the records, then all the records till that point would be loaded to setup tables and all the records after that point of time will be moved to extraction queue or update tables. My question is, if this is true why would we ever need to lock the system during setup tables filling?
>
>     If you say the records after that particular time and date (10pm, 12-31-2007) will not be collected in extraction queue and update tables, why don't we do the following
>
>              a). say, I do full load with end date and time (10pm 12-31-2007)
>              b). Next, I do delta init with start date and time (10pm 12-31-2007) (this time I lock the postings)
>
>          If we do this way, we can actually reduce the down time of the system. Is my conclusion right?
>
>          If you say it's not practicable as some transactions' saving time differs from time stamp and some transactions' delta is even measured by pointer.......if this is the case we can use Delta offset. What do you say about this?
This is applicable to Generic Delta where you can set the Safety Interval (Upper Limit and lower Limit) for the extractor based on ALE Pointer, or Time Stamp or Calendar day.
If you excute a extractor with early delta init, during the setup table fill, the delta records will be directly written to the delta queue. The delta management handles these functionality.
[How to Create Generic Delta|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/84bf4d68-0601-0010-13b5-b062adbb3e33]
[SAP BI Generic Extraction Using a Function Module|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33]
4
>
curious maven wrote:
How this scenario differs to early delta initialization?
If you do a Init without Early Delta init, then the user cannot post new documents and you have to either schedule in the weekend or request for a Source System downtime.
But if you use Early delta , then you don't need the source system down time and the user can post new records during the init, which will be written to the delta queue directly.
[How to Minimize Effects of Planned Downtime (NW7.0)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/901c5703-f197-2910-e290-a2851d1bf3bb]
[How to Minimize Downtime for Delta Initialization (NW2004)|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5d51aa90-0201-0010-749e-d6b993c7a0d6]
Thanks
Chandran

What is the Data flow in SAP-BPC NW

Hi All,
Could any body explain me how the data is flowing in SAP-BPC NW.
and what are the steps for Planning
and what are the steps for Consolidation
Regards,
Setty

Hi,
1) Attributes describe master data like a customer. The country where the customer resides, the industry etc. describe and classify the customer. Attributes are not just the structure/metadata of the characteristics. They are also the content. The following table should visualize what i mean:
customer-no. | name
112 | mcpherson inc.
113 | donalds inc.
2) I think, you are asking about the laods from infopackage. We dont have types of infopackage. But we have one thing called Infopackage group, You can create the IPG with the selction of all infopackages in RSA1-Modelling Area to automate those loads automatically. That means it will trigger only those IP's which have been pooled up in that IGP...
Basically there are three types of loads in Infopackage
Full Upload: This will bring all the records in the BW irrespective of how many times you load.
Init Delta: In this you have 2 options: a) Init with data transfer and b) Init without data transfer. Init without data transfer will just setup your delta and when you do the delta load it will bring all the records. Init with data transfer is similar to the full upload. This brings all the records for the first time and will also setup the delta process. Once the Init is done; you have to do delta for all the subsequent loads.
Delta: This will bring only the changed / modified / added / deleted records from the source to BW.
Hope it helps..
Regards
Lavanya

SAP BPC 10 NW loading data from Infoprovider (data value issue in BPC)

Hi Experts,
We are on SAP BPC 10 - 801 NW - SP05
We are having an error when loading data from infoprovider, we tested in DEV and QA and have similar behaviour: data values which are stored in infoprovider are loaded into BPC model with no differences.
However after make a transport procedure into PROD environment and then loading data into BPC Model something happens: suppose that 100,00 is a data value stored in a BW infoprovider, after loading data into BPC from this infoprovider, different data value is loaded into BPC. E.G 100,0 is in BW , but 10000,0 is store in BPC
Is there any idea to fix it or check it?
Thanks for your answer

Hi Giovanni,
This case occurs with colombian currency and others.
Compare the table TCURX in DEV, QA and PRD.
There must be an entry for currency COP only in PRD.
Like
CURRKEY CURRDEC
COP 0
Note 1240163 explain this behavior.
If you need the value to be stored in 100,00 format in BPC, you can create a routine to convert this value.

Delta functionality between SAP 4.7 and ECC 6

Hi All,
Can anyone please provide me with any documents or links on delta functionality between SAP 4.7 and ECC 6.0 in MM/WM.
Any information would be helpful.
Regards
Prashant

Hello
Following are the basic differences as far as MM Module is concerned;
Pickup list - Batch where-used list display in transaction MB56
u2022 Until release 4.7, the top-down and bottom-up analyses in the function pickup list for batch where-used list (transaction MB5C) were displayed only in the form of simple output lists. As of release 6.00 of SAP ERP Central Component, the function pickup list for batch where-used list branches to the batch where-used list itself (transaction MB56).
u2022 In addition, user can define how the data in the batch where-used list is displayed, in the initial screen.
u2022 User can use all the settings available in the batch where-used list. For example, he can expand transfer posting or display vendor batch. However, it is not possible to limit the selection to valid plants in the initial screen of the pickup list.
Usability enhancements for transaction MIGO for the posting of goods movements
u2022 For goods movements that refer to purchase orders as reference documents (for example, goods receipt, goods issue, subsequent adjustment), user can specify the ordering plant as an additional selection criterion directly next to the purchase order number and the item number.
u2022 There is a new default value: "copy account assignment fields." When entering other goods receipts, user can copy existing account assignment data from the previous item to use as the default values for a new item. To do this, user has to set the copy account assignment fields indicator in the default values.
u2022 User changes the default values in the menu path "Settings -> Default Values."
u2022 Goods movement is monitored with reference to a material document. When you enter the following goods movements, it is possible to specify a material document, such as the following, as the reference document:
Goods receipt
Goods issue
Transfer posting
Remove from storage
u2022 Note that these material documents must be documents that have arisen from a goods movement without reference ("Others") and that are not reversal documents.
New report : display list of invoice documents (MIR5)
u2022 Logistics invoice verification offers a new report display list of invoice documents (RMMR1MDI), w hich user can use to display such a list (Transaction is MIR5).
u2022 As an addition to the existing program invoice overview (transaction code MIR6), user have extended selection criteria and display options. For example, on the initial screen user can make selections by one-time customers, invoice gross amount, and entry date.
u2022 User can also show an expert mode, which enables him to select at plant level by FI document, GL A/c posting, and Material Posting.
u2022 In the output list, the report shows both posted and held invoices.
u2022 It does not show invoices without a corresponding FI document; such as invoices planned for verification in the background or which the software has already verified as containing errors.
Requirement prioritizations in materials management
u2022 With Requirement Prioritization functionality user can assign requirement urgency at item level in purchasing and reservation documents.
u2022 The software determines the relevant requirement priority (overall priority) of a material requisition from the combination of requirement urgency group and organizational priority.
Mass maintenance of outline agreements
The following two transactions available:
u2022 Mass maintenance for contracts: transaction code MEMASSCONTRACT
u2022 Mass maintenance for scheduling agreements: transaction code MEMASSSA
Commitment plan for purchase contracts
u2022 With the function of the commitment plan for purchase contracts, it is possible to pre plan value consumption for a purchase contract.
u2022 To this end, a commitment plan is generated for each document item of the relevant contract.
u2022 This commitment plan itself can have any number of items.
u2022 User can define a value and a validity date for each commitment plan item.
u2022 This enables user to pre plan different values for different periods of time.
u2022 The software generates an earmarked fund document for a defined commitment plan item.
u2022 This earmarked funds document can in turn contain several different items with different account assignments.
u2022 The software adopts these account assignments from the item account assignments of the commitment plan.
u2022 If a purchase requisition or purchase order references this contract, the earmarked funds document is copied into the purchase order, and the account assignment is adopted from that document.
u2022 Account assignment to a different account assignment object is then no longer allowed.
Availability check in "Enjoy purchase order and requisition"
u2022 Display and checking of availability are invokable separately in the "Enjoy purchase order and requisition" function, in line with the software behavior on the sales side.
u2022 User invoke the display and checking of availability in the "Enjoy purchase order" function (transaction code ME21N) and the "Enjoy purchase requisition" function (transaction code ME51N) as follows:
To display the availability overview, choose the menu path "Environment -> Availability." - To check availability, choose the "Check Availability" icon.
Until this release, if user carried out the availability check for an item of a stock transport order, the software adopted confirmations as per the desired date/time only.
u2022 Two settings are possible with availability check:
Confirmation as per desired date/time (this is the standard setting and corresponds to previous software behavior)
Delivery proposal - Full confirmation
External services: putting service items in the purchase order on hold (changed)
User can put purchase orders with service items on hold if these items do not contain any errors. Purchase orders with service items can also be put on hold if errors occur only at header level or as a result of the availability check.
Customizing transactions OX18 replaced by view
The assigned customizing transactions have been replaced by the following view in the following implementation guide activity in customizing for the enterprise structure: Assign plant to company code: transaction OX18 replaced by view V_T001K_Assign. One will find this activity in the implementation guide under the menu path "Enterprise Structure -> Assignment -> Logistics General -> Assign Plant to Company Code."
Goods receipt: new movement types in inventory management
The following new movement types are available in inventory management:
107: Goods receipt to valuated goods receipt blocked stock
109: Goods receipt from valuated goods receipt blocked stock
Prepayment of invoices
This functionality is characterized as follows:
u2022 User can trigger prepayment of vendor invoices in logistics invoice verification.
u2022 User use the prepayment function for vendors with whom organisation has a good, long-standing relationship.
u2022 The function enables payment soon after issue of the invoice and full exploitation of the date of required payment and existing cash discounts, by posting the vendor liabilities, taxes, and cash discounts in financial accounting in advance.
u2022 The software executes the payment of the invoice regardless of the relevant goods receipt and the outcome of the invoice verification check.
u2022 Most logistics invoice verification standard functions are not affected by the prepayment function.
u2022 When the software posts invoices, it continues to execute the standard checks.
u2022 If the software has already posted the prepayment document, user can make only restricted changes to the header fields of the invoice.
u2022 To ensure adequate and orderly financial accounting postings, a prepayment clearing account has been added to SAP ERP Central Component.
u2022 Upon prepayment, the software debits this account and then settles the account again after executing the check.
Purchasing accounting information to the former SAP Business Information Warehouse
u2022 With the transfer of the purchasing account information to the former SAP Business Information Warehouse component (whose functionality is now part of SAP Net Weaver), it is now possible to maintain Info Cubes, reports, and queries that can determine how and where the costs from purchasing documents have been assigned and controlled.
u2022 As part of the software, a new data source (2LIS_02_ACC) has been created and the purchasing extraction process extended to cover the account information for purchasing orders, schedule agreements, and contracts.
Automatic settlement of planned delivery costs with evaluated receipt settlement (MRDC)
u2022 A new report (RMMR1MDC), available within the logistics invoice verification, can be used to automatically settle planned delivery costs.
u2022 To invoke the report, from the SAP easy access screen, choose the menu path "Logistics -> Materials Management -> Logistics Invoice Verification -> Automatic Settlement -> Automatic Delivery Cost Settlement" (transaction code MRDC).
u2022 Functionality for report RMMR1MRS is enhanced.
u2022 User can use the report RMMR1MRS, "Evaluated receipt settlement with logistics invoice verification (LIV)" (transaction code MRRL), to settle planned delivery costs in addition to goods and service items within logistics invoice verification.
u2022 To do so, set the relevant indicator on the initial screen of the report.
Parking service items
It is now possible to put service orders without errors or with commitment errors on hold.
Report MB5B : Stock on Posting Date
u2022 This Report is available with "Non-Hierarchy" display option which provides details of Opening, Receipt, Issue and Closing balances of Stock with quantity and value both for a given period.
u2022 This functionality is not available in Release 4.7.
Stock Transfer Between Storage Locations
u2022 Function of stock transport orders between storage locations is available from ECC 6.0 onwards.
u2022 As a result of which user can input issuing storage location with supplying plant.
u2022 Facility of using different delivery types for different issuing storage locations is available.
u2022 Shipping Point data can also be determined based on the issuing storage location.
If u want to know more go through the following links
http://solutionbrowser.erp.sap.fmpmedia.com/
http://help.sap.com/saphelperp2005vp/helpdata/en/43/6880cbb88f297ee10000000a422035/frameset.htm_
https://wiki.sdn.sap.com/wiki/display/ERP6/ERP2005+Upgrade
check following
http://help.sap.com/bp_bblibrary/500/html/U40_EN_IN.htm
for more help check following
http://help.sap.com/bp_bblibrary/500/BBlibrary_start.htm
Go through the following link for the Delta functionality notes
http://solutionbrowser.erp.sap.fmpmedia.com/
Regards
Priyanka.P

SAP BPC using SAP Netweaver

Hi
Would please somebody give me a link on how to educate myself on SAP BPC using SAP Netweaver
Thank you very much in advance
Zubzero

Hi,
You are right. The link is like MS platform only. This is because there are not much differences between the 2 platforms. Few of the differences would be
1. BPC NW is integrated with NW BI
2. BPF is not available in BPC NW 7.0. However, it is back in 7.5
3. Increased dimensionality
3. Integration with BI accelerators
4. Improved dynamic templates
5. Books are not available
6. Transports are available.
There is a book BPC 330, which will give you a better understanding of BPC NW. This book is only available on classroom trainings.
Hope this helps.

How to use the RateEntity dimension in SAP BPC?

Hello everbody,
I am implementing a consolidation process using SAP BPC. I want to use the RateEntity dimension, to translate a same currency into different exchange rates depending on the company.
I want the company which ID is GFU (which is from Brazil) in LegalEntity dimension is converted using a special exchange rate. I have added a GFU member in RateEntity dimension, and I have entered the exchange rates for the member GFU and for the member Global in RateEntity dimension.
But the problem is that after I run the FX Restatement package, converted data for this company is not the proper one, because Global exchange rates have been used instead of GFU exchange rates. Does anybody know why? Do I have to do anything else?
Thank you very much for your time

Do you see the search functionality in the upper left of the screen?
Okay, now type in ecatt, press enter and in the next screen filter on blogs.

Transport of Delta Initializations in SAP BPC 10

Similar Messages

Maybe you are looking for