Project Billing burden transactions must be accounted for, but not billed to the customer.

Hello Community Members,We are facing a business requirement in Oracle Projects Cloud where burden transactions must be accounted for, but not billed to the customer. Additionally, each burden expenditure type must generate separate accounting lines for proper GL mapping through SLA rules.Key Requirement:

• We must generate distinct burden transactions for each burden expenditure type to allow different SLA rules to apply.
• We cannot calculate burden within the raw cost transaction (as that results in only one summarized burden line), which is not acceptable for our users due to accounting requirements.
• These burden transactions must not be billed, but accounting still needs to be generated for them.