Message type: E = Error
Message class: BIL - General billing
Message number: 017
Message text: Secondary installation &1: No billing doc. available from installation &2
Secondary installation &v1& does not have a matching billing document
for secondary installation &v2&.
Background:
You bill the <DS:DE.MAININST>primary installation</> in an installation
group. The primary installation requires data from secondary
installations and therefore simulates billing for the secondary
installations. You defined the secondary installation &v2& as the
<DS:DE.HIGHLEVINST>higher-level installation</> for the secondary
installation &v1&. A variant program interprets this hierarcha as a <ZH>
serial switching</>. The consumption at secondary installation &v1& must
be deducted from the consumption at secondary installation &v2&. The
difference is calculated at billing document level. That is, the
consumption from the simulated billing document for installation &v1& is
to be deducted from the consumption from a billing document for
installation &v2&.
The billing period <DS:DE.BEGABRPE>begins</> on &v3& and
<DS:DE.ENDABRPE>ends</> on &v4& in the billing document for secondary
installation &v1&. However, the system was unable to find a suitable
billing document for installation &v2& for this period.
Possible reasons for this error:
There is no contract in this period for secondary installation &v2&.
This is not allowed if there is still a contract for the higher-level
secondary installation.
However, the two installations have different <DS:DE.INSTROLE>
installation roles</> with different forms of
<DS:SIMG._ISUBIBDRS_000078>data exchange from the secondary installation
to the primary installation</>. The consumption for secondary
installation &v1& is entered in an input operand but not the consumption
for secondary installation &v2&.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Specify a contract or align data exchange accordingly for the
installation roles.
Error message extract from SAP system. Copyright SAP SE.
BIL017
- Secondary installation &1: No billing doc. available from installation &2 ?The SAP error message BIL017 indicates that there is no billing document available for a secondary installation in the context of billing processes. This error typically arises in scenarios involving utility billing or similar processes where installations are linked to billing documents.
Cause: The error message BIL017 can occur due to several reasons: Missing Billing Document: The primary cause is that there is no billing document created for the specified secondary installation. This could be due to a failure in the billing process or the document not being generated. Incorrect Configuration: There may be configuration issues in the billing setup, such as incorrect assignment of installations or billing types. Data Inconsistencies: There could be inconsistencies in the master data related to the installations or billing documents. Timing Issues: The billing document may not have been created yet due to timing issues in the billing cycle. Authorization Issues: The user may not have the necessary authorizations to view
Get instant SAP help. Sign up for our Free Essentials Plan.
BIL016
The hierarchy for secondary installation &1 changes on &2
What causes this issue? The hierarchy defined by specifying a <DS:DE.HIGHLEVINST>higher-level installation</> will change on &v2&...
BIL015
Installation &1 does not have a clear hierarchy level
What causes this issue? A <DS:DE.HIGHLEVINST>higher-level installation</> is entered for secondary installation &v1& on &v2&a...
BIL018
Secondary installation &1: Billing period of higher-level inst. not valid
What causes this issue? The <DS:DE.BEGABRPE>start of the billing period</>, &v3&, does not match &v4&, which is specified...
BIL019
Secondary installation &1: Billing period of higher-level inst. not valid
What causes this issue? The <DS:DE.ENDABRPE>end of the billing period</>, &v3&, which is specified for the secondary installation...
Click on this link to search all SAP messages.