Projects Cross-charge functionality Vs Inter-project Billing

Hi,
We are currently evaluating the funtionalities of Project Cross Charge Vs Inter-project billing. Our setup is such that we have 3 Legal Entities, 3 Business groups, 3 SOB's and 3 operating units, each tied to their own legal entity, Business group and Set of Bools. When reviewing the documentation, it looks like the Cross charge functionality does not support operating units that are in two different business groups. Does that imply that we have use the Inter-project billing to charge projects across operating units.
We will really appeciate, if one can provide some additional insight in this regard.
Regards,
- Vasu Krishnaswamy -

Hi,
It is possible to have cross charge across the Business groups. It is also mentioned in Oracle Projects fundamentals guide. Please refer to the Global Project Support Chapter. Below is the extract from it.
Providing Data Access Across Business Groups
Global enterprises have resources and projects that are located, managed, and accounted
for in different business groups or different countries. To meet the needs of these
enterprises, Oracle Projects provides the following functionality:
• Globally located resources can charge their time and expenses to projects that are
owned outside their respective business groups.
• Resources can manage and administer projects located in different business groups.
• Oracle Projects produces appropriate accounting entries, intercompany invoices, and
management reports even if the resource organization and project owning
organization have different accounting calendars and job definitions.
This functionality is provided through the use of global organization hierarchies, global
jobs, and cross charge functionality.
Hope this helps!
Thanks,
Sathish
www.projectsaccounting.com

Similar Messages

Capital Project Cross Charge

Hi,
Our client want to use Cross charge (Across SOBs) for a capital project. As per the metalink note cross charge is not allowed for capital project.
Any workaround to use cross charge for a capital project
thanks in advance
Govind

Hi
I assume you want the project to capitalize assets on the owning organization SOB.
The costs incurred by other OU should not generate assets for the provider OU, only internal revenue or cost recover.
You may consider the inter project billing functionality where the receiver project is the capital project, while other OU are charging a provider project. The provider project will bill the capital project.
Dina

Does there is any restrictions of Cross Charg processing on Capital Project

Hello Experts,
Can you please help me in understanding about the restrictions of cross charging on CAPITAL CLASS of Oracle Projects?
If yes then can you please let me know the restrictions / exceptions.?
Thanks
:-)

Hi Dina,
We have a situation where all our capital projects are in US but employees OTL timecards entered for those projects going into OU/LE where emp belongs (Example- UK employee timecard imported in UK OU for the work he did for US capital project). Beause the cost for the labor transactions must be processed in the OU in which the project resides, labor hrs entered in UK is not picked by costing process. How to resolve this? We really don't use cross presently and don't want to use in future for capital projects? Is any way we can transfer approved expenditure batch to US?
Thanks
R

Need the exact difference betwn Intercompany Billing and Inter-project bill

Hi,
Can any one tell me the exact difference between the intercompany Billing and inter-project billing?
The decision to which should be used in which scenraios.
also what is the Setup Level Difference in both.
If you have any white paper / document / note in metalink also on this topic then I will be very happy to have that.
Thanks very much in advance.
Regards

Hi
Inter project billing may be used within the same operating unit.
Intercompany billing may be used only accross operating units.
Inter project billing means the provider organization is charging a separate provider project.
With intercompany billing provider organization is charging the same project as of the receiver organization.
With inter project billing the provider project may bill the receiver in any billing method as any contract project. With intercompany billing the billing is based on transfer price rules which may be only applied to actual expenditures of the provider organization.
There is full list of all setup steps in Oracle Projects Implementation user guide.
Dina

Inter Project Billing - Questions

Hi,
We have setup Inter Project billing and the process works as expected.
But we still have questions about the Accounting Process - do the ap invoice and the ar invoice hit the same account? and how do we clear the Open Invoices on both AP and AR?
Please Help!!!!
Thanks,
Akshaj

Hi Dina,
A couple more questions.
Following is a table with example transactions below:
GL     Cust. Proj     Internal Proj.     Consolidated
Sales           400
IP-Sales               (200)     (200)
COS               200     200
IP-COS          200          200
Clearing     (200)               (200)
Net Income          200      0
1.     Should the UBR / UER be an internal UBR/UER. Would it not otherwise murky up the UBR/UER for contract projects?
2.     How do the Internal Project and the Customer Project rollup on the GL ? Do we need to have a consolidation project to net IP-Sales and IP-COS
3.     Also - how do we handle scenarios where COS in the internal project is greater than the revenue/billed amount? How does this rollup to the Customer Project?
Please advise.
Thanks.

Inter Project Dependency Reporting - Options

Hello,
A client I'm working for has requested the ability to see inter-project dependencies across a group of projects (e.g. Program or Portfolio grouping) with a critical path visible throughout, allowing the user to see where a critical path existing across multiple
projects.
Is this possible without having to 'daisy chain' projects via the Subprojects button, or via a custom SSRS report? This is key functionality and we come across this deficiency on every client engagement.
Environment: EPM 2013
Thanks in advance.
Nock

Hi Nock,
I'd suggest you to insert your sub-projects into a master project. By default, each inserted project is calculated like summary task:
Thus calculating the critical path on your master project with this option checked will give you the overall critical path.
Critical path means depedencies between tasks thus I believe you have to go through using sub-projects and links.
Hope this helps,
Guillaume Rouyre, MBA, MVP, P-Seller |

Cross company LIV without a Inter-company billing

Hi,
Is it possible to post a FI-customer invoice (FB70) in Company A by posting a LIV in Company Code B. Currently Company A does not have a Sales/Purchasing organization setup. Requirement for a PO in Company B is, to track the products and monitor the sales.
The standard (EDI) inter-company billing needs a order/billing to be created in Company A.

Hi,
Check these notes:
SAP Note 109254 - Customizing stock transport order Cross Company
SAP Note 338922 - Analysis note for cross-company transactions (delivery)
SAP Note 543821 - FAQ: cross-company processing
Regards
Eduardo

Urgent: Can Overtime hours be directly charged to a WBS, Project etc.

Dear Team:
Can Overtime hours be directly charged to a WBS, Project etc.
Let me have a Business Solution as well as the SAP solution to do the same requirement.
For example:
If an employee has worked for a Project - Instrumentation for 8 hours + 4 hours as overtime. The total 12 hours to be charged to Instrumentation Project.
Currently we are following as 8 hours are charged directly to the Project using Project Systems Data Entry Profile and 4 hours overtime using HR Data Entry Profile. These overtime hours are not getting directly charged to the Project but these are getting paid.
How the above 4 hours of overtime be charged against a project as well as to be paid as overtime. Please assist.
Regards
Mallikarjun P
[email protected]

I didn't get you. Please could you explain me clearly.
Now my scenario is as follows:
If an employee has worked for a project he would be recording his man hours using the Project Systems Profile. For example he has worked on 24.03.2008 for 10 hours for an X project. He books the 10 hours in the project, but in this case 2 hours is overtime to be paid, so he goes to the HR Data entry profile and books the 2 hours as overtime for date 24.03.2008. These 2 hours are recorded in infotype 2002 and payment is made as per the calculation.
10 hours which went to Project Systems will be based on some fixed amount per hour as per the settings. But these 2 hours cost which was paid as overtime in HR should be reflected in the project instead of the normal cost which was set in PS.
More clear:
Project Systems - 1 hour rate is Rs.30.
Human Resources - 1 hour overtime is Rs.100.
If 10 hours worked in Project, 8 hours * 30 = Rs.240 charged to a project.
But 2 hours overtime = 2 hours * 100 = Rs.200 should be charged to the Project and also should be paid as overtime.
Please update on the same.
Regards
Mallikarjun P
Edited by: Patlolla Mallikarjun on Apr 2, 2008 11:58 AM

Open Other Project - Does Not Function

Hello -
We are finishing a CBT lesson in Cap 3 which includes 29
seperate projects. At the end of each project the student is
presented a button to take them to the next project, i.e. "Open
Other Project".
Here lies the issue, we have set this button to "Open other
project" and "Open URL or file". In both case the next project does
not open. The user is taken to an internet search page. We set up
the button "On Success" feature using the Captivate Help files
where it instructs you to remove all of the system paths and just
use the project or file names. Also confirmed button settings in
Advanced Interaction.
We are publishing our projects in .exe formats. This isuue is
present when we preview it using the preview feature and from the
.exe products.
What are we doing wrong, any ideas?

Hi again
I just conducted a brief test using a Button object and the
exact file names you listed. Things worked as expected on my end.
This is actually good news, as it suggests Captivate 3 isn't to
blame. Instead, something is wonky with your project(s).
One thing that strikes me here is that you say you are seeing
a Web Browser open. This suggests your button is programmed to
"Open URL or File" and not "Open other project". You may wish to
double check that. If you examine it and it already says "Open
other project", you may wish to delete that button and insert a new
one. Maybe somehow it became corrupt and is retaining the Open URL
or File setting and not respecting the Open other project setting.
Cheers... Rick

Inter-project Liability Posting

Hi,
I need some advice here in project system.
My company is planning to use project system to manage the project related activity, revenue and spending.
One of the common business scenario that happen is the sharing of resource between projects.
In this case, we would like to see whether we can recording this transaction as a liability from one project to the other project.
Meaning, we will have internal accounts payables and internal accounts receivable which representing the respective project in the system.
What do you think I can do in the system to achieve this?
I was thinking about using special AR/AP account group to handle this situation.
Please advice.
Regards,
Cheah

Resources will be available at a specific work center. You will assign resources from work center to different projects, Now i dont understand how a project will be liable to another project.

Inter company Billing for service industry

Hi,
I never workded over inter company billing.Please suggest me what to do? I am in a service industry project where no delivery takes place.So how should i go about for intercompany billing configuration?
Thanx in advance.
Regardds,
Satya

Dear Satya,
You can create the inter company bill with refrence to the service order
To do inter company billing settings go through this IMG path
IMG>Sales and Distribution>Billing-->Intercompany billing
Process steps for normal inter company process with delivery.
INTER COMPANY BILLING
Definition:
A company arranges direct delivery of the goods to the customer from the stocks of another company belonging to the same corporate group.
To put in simple terms, Company code A orders goods through its sales organization A from Plant B belonging to Company code B.
It is imperative that both Plants A & B should have the material. In other words, the material is created for both the Plants A & B + their respective storage locations.
Sales Organizations and Plants are uniquely assigned to Company codes. It is not possible to assign either a plant or a sales organization to more than one company code.
Sales organizations and plants assigned to each other need not belong to the same company code.
In other terms, a plant belonging to Company code A & assigned to Sales Organization A can also be assigned to Sales Organization B of Company Code B. This enables cross company sales.
PARTIES INVOLVED
1) End Customer 2) Ordering Company code 3) Supplying Company Code.
End customer:
Customer who orders goods from the ordering company code.
Ordering Company Code:
Which orders goods from Plant belonging to Supplying Company code through its sales organization and bills the end customer.
Supplying Company Code:
Supplies goods from its plant to the end customer specified by the ordering company code and bill the ordering company code.
CONFIGURATION SETTINGS
Assign Delivery Plant of the supplying company code to Sales Org + Distribution channel of the Ordering company code in the Enterprise Structure.
DEFINE ORDER TYPES FOR INTERCOMPNY BILLING:
Menu path: IMG/ SD/Billing/Intercompany Billing/Define Order Types for Intercompany billing
Assign Organizational units by Plant:
Menu Path: IMG/ SD/Billing/Intercompany Billing/Assign Organizational units by Plant.
Define Internal Customer Number By Sales Organization:
Menu Path: IMG/ SD / Billing/ Intercompany Billing/ Define Internal Customer Number By Sales Organization:
Creating / Showing Ordering Sales Organization as Internal Customer for Supplying Company code:
Transaction Code: XD01
The ordering sales organization is represented as Internal customer of Supplying company code.
We need to create customer master in Account Group - Sold to Party and maintain minimum required financial & Sales Area data.
This internal customer number has to be assigned to the ordering sales organization. Hence, the system automatically picks up this Internal customer number whenever there is Intercompany billing.
PRICING:
We need to maintain two pricing procedures RVAA01 & ICAA01. Pricing procedure RVAA01 represents condition type PR00 & any other discounts or surcharges that are meant for end customer.
We assign Pricing procedure RVAA01 to combination of Sales area (Of Ordering company code) + Customer Pricing Procedure + Document Pricing Procedure of Sales document type.
This pricing Procedure (RVAA01) is determined both at Sales Order level & Billing processing for the end customer. We maintain PR00 condition type to represent the ordering company code's price to the end customer.
Condition records for PR00 are maintained using organizational elements of Ordering company code, end customer & the Material.
Eg: Sales Org. of Ordering company code + End customer + Material.
We also need to maintain PI01 condition type to represent costs to Ordering company code (in other words revenue to supplying company code). It is statistical condition type & meant for information purpose only.
Condition records for PI01 are created with the following key combination:
Ordering sales Org + Supplying Plant + Material
Pricing Procedure ICAA01is determined at Intercompany billing processing level.
Pricing Procedure ICAA01 - Pricing Procedure for Inter company billing is assigned to the combination of: Sales Area (of supplying company code) + Document pricing Procedure of Billing document type IV + Customer Pricing Procedure of the Internal customer.
Pricing Procedure ICAA01 has condition type IV01 that represents revenues for Supplying company code in the intercompany billing.
PR00 condition type also appears in Intercompany billing document. It is for information purposes only and does not have bearing on the value of the document.
PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
In your requirenment there will not be delivery process in between service sales order and the intercompany bill so do the settings accordingly in the copy controls between service sales order type and inter company billing type.
I hope this will help you,
Regards,
Murali.
I hope this will help you,

How to create cross charge AP invoice through Payables Open Interface Import

Hi,
I am working on developing an AP invoice interface program for creating cross charge invoices in Oracle 11i.
Cross charge invoice means the supplier & site is from operating unit A, but the costing should hit the project number in Operating unit B.
The pa_projects_all.allow_cross_charge_flag for the project number is set to Y. I am using below scripts to enter data into the interface tables:
<code>
INSERT INTO ap_invoice_lines_interface
                           (invoice_id,
                            invoice_line_id, line_type_lookup_code,
                            amount, org_id,
                            last_update_date, last_updated_by,
                            creation_date, created_by,
                            project_id, task_id,
                            expenditure_type, expenditure_item_date,
                            expenditure_organization_id
                    VALUES (v_invoice_id,
                            ap_invoice_lines_interface_s.NEXTVAL, 'ITEM',
                            c_line.invoice_amount, v_org_id,
                            TRUNC (SYSDATE), fnd_global.user_id,
                            TRUNC (SYSDATE), fnd_global.user_id,
                            v_project_id, v_task_id,
                            v_expenditure_type, v_expenditure_item_date,
                            v_organization_id
INSERT INTO ap_invoices_interface
                     (invoice_id, invoice_num, invoice_date,
                      gl_date, vendor_id, vendor_site_id,
                      invoice_amount, invoice_currency_code,
                      exchange_rate, exchange_rate_type, exchange_date,
                      terms_id, terms_date, payment_method_lookup_code,
                      pay_group_lookup_code, payment_currency_code,
                      last_update_date, last_updated_by, creation_date,
                      created_by, SOURCE, org_id
              VALUES (v_invoice_id, c_head.invoice_num, c_head.invoice_date,
                      c_head.gl_date, v_vendor_id, v_vendor_site_id,
                      c_head.invoice_amount, c_head.invoice_currency,
                      v_rate, 'Corporate', c_head.invoice_date,
                      v_terms_id, TRUNC (SYSDATE), v_payment_method,
                      v_paygroup, c_head.payment_currency,
                      TRUNC (SYSDATE), fnd_global.user_id, TRUNC (SYSDATE),
                      fnd_global.user_id, 'CONCUR', v_org_id
<code>
After inserting data into the interface tables, I submitted the Payable Open Interface Import with correct source and the record fails with below errors:
REASON                         DESCRIPTION
Account Required             An account is required
PA Flexbuild Failed          Project Flexbuilder failed with error
The above inserts are working fine for same entity invoices.
I am not sure what could be the error.
Any help is greatly appreciated.
Thanks
Imran

Have you customized/setup the Project Accounting Workflow builder. You need to do some setup for this workflow builder so that the project accounts can be derived properly.

Inter company Billing document not created

Hi,
I am in a service industry project where invoicing is done through order ,no delivery takes place.I have done configuration related to inter company billing like Assign inter company billing type to Order ,assign plant sales area and internal customer to the ordering Sales Organisation.
After this we are able to invoice the external customer but when we are trying to create inter company billiing document through the same order a log is created which says"Item already fully invoiced"
What should i do now?
Plz suggest.
Regards,
Satya

Luk we are using quantity contract and through that we do DP91 for resource related billing which generate a Billing Request where sales document category is L (debit memo request) and then we billed that billing request to the end customer.But when i again use that billing request for inter company billing system says "item is fully invoiced"
Now tell me what should i do?
Regards,
Satya

Inter company billing use and steps?

Inter company billing use and steps?

INTERCOMPANY BILLING
Definition:
A company arranges direct delivery of the goods to the customer from the stocks of another company belonging to the same corporate group.
To put in simple terms, Company code A orders goods through its sales organization A from Plant B belonging to Company code B.
It is imperative that both Plants A & B should have the material. In other words, the material is created for both the Plants A & B + their respective storage locations.
Sales Organizations and Plants are uniquely assigned to Company codes. It is not possible to assign either a plant or a sales organization to more than one company code.
Sales organizations and plants assigned to each other need not belong to the same company code.
In other terms, a plant belonging to Company code A & assigned to Sales Organization A can also be assigned to Sales Organization B of Company Code B. This enables cross company sales.
PARTIES INVOLVED
1) End Customer 2) Ordering Company code 3) Supplying Company Code.
End customer:
Customer who orders goods from the ordering company code.
Ordering Company Code:
Which orders goods from Plant belonging to Supplying Company code through its sales organization and bills the end customer.
Supplying Company Code:
Supplies goods from its plant to the end customer specified by the ordering company code and bill the ordering company code.
CONFIGURATION SETTINGS
Assign Delivery Plant of the supplying company code to Sales Org + Distribution channel of the Ordering company code in the Enterprise Structure.
DEFINE ORDER TYPES FOR INTERCOMPNY BILLING:
Menu path: IMG/ SD/Billing/Intercompany Billing/Define Order Types for Intercompany billing
Assign Organizational units by Plant:
Menu Path: IMG/ SD/Billing/Intercompany Billing/Assign Organizational units by Plant.
Define Internal Customer Number By Sales Organization:
Menu Path: IMG/ SD / Billing/ Intercompany Billing/ Define Internal Customer Number By Sales Organization:
Creating / Showing Ordering Sales Organization as Internal Customer for Supplying Company code:
Transaction Code: XD01
The ordering sales organization is represented as Internal customer of Supplying company code.
We need to create customer master in Account Group Sold to Party and maintain minimum required financial & Sales Area data.
This internal customer number has to be assigned to the ordering sales organization. Hence, the system automatically picks up this Internal customer number whenever there is Intercompany billing.
PRICING:
We need to maintain two pricing procedures RVAA01 & ICAA01. Pricing procedure RVAA01 represents condition type PR00 & any other discounts or surcharges that are meant for end customer.
We assign Pricing procedure RVAA01 to combination of Sales area (Of Ordering company code) + Customer Pricing Procedure + Document Pricing Procedure of Sales document type.
This pricing Procedure (RVAA01) is determined both at Sales Order level & Billing processing for the end customer.
We maintain PR00 condition type to represent the ordering company codes price to the end customer.
Condition records for PR00 are maintained using organizational elements of Ordering company code, end customer & the Material.
Eg: Sales Org. of Ordering company code + End customer + Material.
We also need to maintain PI01 condition type to represent costs to Ordering company code (in other words revenue to supplying company code). It is statistical condition type & meant for information purpose only.
Condition records for PI01 are created with the following key combination:
Ordering sales Org + Supplying Plant + Material
Pricing Procedure ICAA01is determined at Intercompany billing processing level.
Pricing Procedure ICAA01 Pricing Procedure for Inter company billing is assigned to the combination of:
1) Sales Area (of supplying company code) + Document pricing Procedure of Billing document type IV + Customer Pricing Procedure of the Internal customer.
Pricing Procedure ICAA01 has condition type IV01 that represents revenues for Supplying company code in the intercompany billing.
PR00 condition type also appears in Intercompany billing document. It is for information purposes only and does not have bearing on the value of the document.
PI01 represented under pricing procedure RVAA01 is reference condition type for IV01 and the same is defined in the condition type IV01. Due to this these two condition types represent same value.
The condition type IV01 in intercompany billing document represents revenue to the Supplying Company. But its corresponding condition type PI01 in the billing document to the end customer is shown as a statistical item meant for information purposes.
Condition Type VPRS in the intercompany-billing document indicates cost to the supplying company code.
The use of two different condition types in Intercompany billing is necessary to ensure that data is transmitted correctly to the financial statement (Component CO-PA).
ILLUSTRATION:
STEP 1: Create Sales Order
Manually Enter the Delivery Plant of the Supplying Company Code:
OBSERVE CONDITIONS SCREEN FOR ITEM:
PR00 represents Price to the end customer (in other words, revenue for the ordering company).
PI01 represents cost to ordering company (in other words, revenue for the supplying company). It is represented as statistical item only.
DELIVERY:
Delivery is carried out from the supplying point & hence we can observe that it is done from shipping point assigned to the supplying point.
Subsequently, Picking & PGI are carried out.
BILLING TO END CUSTOMER:
T-Code: VF01
Create Intercompany Billing:
T-code: VF01
OBSERVE THE CONDITIONS SCREEN OF THE INTERNAL INVOICE:
IV01 Condition type represents revenue for the supplying company code.
VPRS condition type represents cost to the supplying company code.
PR00 in intercompany billing document displays amount billed to the end customer. It serves as just an information item and is inactive.
If the ordering company enters the incoming invoice manually, the delivering company can print out an invoice document with the help of output type RD00, which is then sent to the Payer.
If automatic invoice receipt has been agreed, we must use the SD output control functions to ensure that output type RD04 is found in internal billing. In R/3 system, output determination procedure V40000, which includes this output type, is assigned to Intercompany billing type IV.
The automatic posting to the vendor account is initiated when output type RD04 is processed. The system uses the EDI output type INVOIC in the FI variant.
To ensure that payables are posted in financial accounts of the ordering company, the delivery company must be created as a vendor.
Configure Intercompany Stock Transport Order
Material should exist in both the plants (Delivering & Ordering),
Internal customer should be assaigned to the ordering plant ( MM -> Purchasing -> Purchase Order -> Setup stock transport order -> assign the internal customer to the ordering plant and assign the Sales area of the internal customer.
Assign its Sales area to the delivering plant
Assign the document type and Delivery type NB and NLCC
Assign the Supplying plant --> Receiving Plant --> NB
Take the delivering plant and assign the sales area.
Vendor master has to be created and assaign the supply source ( Delivering Plant).
Create a puchase order ME21N ---> Save
Delivery VL10 G ---> Calculation rule (appropriate) --> Assaign the purchase order number here and execute.
Select the Delivery creation line and do the back ground process.
Start the log display and see the delivery document number by the documents button
Goto VL02N --> do picking and PGI --> Then do the MIGO with

Error while Doing Inter Company Billing.

Hi All,
I am getting error while doing Intercompany Billing.
I have done all the assigment for Inter company Billing.
Now i have done F2 invoice and was trying to do IV billing , the SAP gives error " Sales organization is not defined".
I am not able to trace the solution for this problem.
If someone has face similar error or have idea abt this error,please revert back.
-Akash

Hello,
there are many notes concerning your reuqest:
543821     FAQ: cross-company processing
338922     Analysis note for cross-company transactions (deliv
308989     Consultant note for cross-company transactions
109254     Customizing stock transport order Cross Company
I hope that the information are helpful.
Regards
Claudia
If you are satisfied with the answer, please give Reward Points

Projects Cross-charge functionality Vs Inter-project Billing

Similar Messages

Maybe you are looking for