SCC - Support Codes for SCM (Services Contracts)

NEEDS TO BE BROKEN OUT INTO SEPARATE TOPICS

What is

These codes are necessary for the successful operation of Services Contracts

Service Contract Maintenance (SCM) introduction
The purpose of the SCM application  is
1.    Record Service Contracs
2.    Validate Service contracts data against referential tables
3.    To create invoicing order lines basis the contract data
a.    Automated invoice order lines. Automatic basis contract data.
b.    Manual invoice order lines. To be created manual by EXPED like app basis contract data.
Related topics
1.    SCC Service Contract Codes
2.    SCI Service Contract Invoicing
3.    SCR Service Contract reporting
4.    SCBCA Service Contracts Bulk Capacity Adjustments (per period)
SCM screens
Main screen
Help ID
Help text
Comment
09672
Contract number.System generated sequential nr.
User can enter own contract number if required. Completion is mandatory.
SCM Contract No {scon01_contract}
09673
Contract date. Defaults system date
User can override with other date I the past if required. Completion is mandatory.
SCM Contract Date {scon01_condate}
09674
Department. User to enter. User entry validated against DEPT. Completion is mandatory.
SCM Department {scon01_dept}
09675
Terminal. User to enter. User entry validated against PHYSCODES Terminal codes. Completion is not mandatory.
SCM Terminal {scon01_terminal}
09676
Contract client. User to enter. This is to record the contractual counterparty. This CLI record will be used for posting invoices by SCI. User entry validated against CLI. Completion is mandatory.
SCM contract Client {scon01_counterparty}
09677
Client contract reference. User to enter. Just for memo purposes. Free format and completion is not mandatory.
SCM Cli Contract reference {scon01_clref}
09678
Invoice client. User to enter. This is to record the CLI acct to which the invoice will be addressed. User entry validated against CLI and completion mandatory.
SCM Invoice Addr Cli {scon01_invaddr}
09679
Business type. This codes for the type of market serviced and the account in the PLR used by SCI when creating the invoice accounting transaction.
User entry validated against SCC business type. Completion is mandatory.
SCM business type {scon01_business}
09680
Contract start date. Date that contract main revenue starts. Can be a date in the future.
User entry validated against date format. Completion mandatory.
SCM Contract start date {scon01_startdate}
09681
Contract end date. Date that contract main revenue ends.
Validate date format, date cannot be bigger than Contract start.
SCM Contract end date
{scon01_enddate}
09682
Extended End date is relevant when the contract end date is not hard defined and is a function of the notice period. Refer to separate section how the contents of this box is supposed to work.
SCM Extended End {scon01_extenddate}
09683
User to enter a number. What the number is is defined by the box right to the number.
SCM Notice period amount {scon01_noticeamt}
09684
This defines the period. The period is taken from the SCC unit codes table when the code is defined as a T(ime) type.
SCM Notice period definition {scon01_noticeperiod}
09685
This is the date notice was given to terminate a notice contract as per notice period.
SCM Notice date {scon01_noticedate}
09686
Invoice period sets the period for invoice creation. Valid codes are SCC unit codes set as T(ime) type.
SCM Invoice Period  {scon01_invperiod}
09687
Invoice method. Defines the method for invoicing. Basically this is a cut off instrument and  defines how to deal with periods and invoicing.  This is relevant  to when the invoice period is M
User can select:
SCM Invoice method {scon01_invmethod}
09688
This is moved to the services grids scon02. Seems to be obsolete as part of scon01.
SCM Invoice day {scon01_invday}
09689
Payment code.This sets the payment condition for all invoices created for the contract.
User entry validated against PHYSCODES payment terms. The SCI will use the data set in this table to calculate the invoice value date.
Completion is mandatory.
SCM Payment code {scon01_payterms}
09690
Contract currency. This is the currency in which the contract is stated and all the invoicing items are denominated in this currency.
User entry validated against CDM. Completion is mandatory.
SCM Contract ccy {scon01_ccy}
09691
Escalation date. This is the date that contract prices might be escalated. Just memo.
Validate date format. Completion is not mandatory.
SCM escalation date  {scon01_escaldate}
09692
Maximum throughput. This is to record maximum throughput for the contract period. Just memo. Free format. Completion is not mandatory.
SCM throughput max {scon01_throughmax}
09693

SCM Automatic Invoice record  {scon02}
09694

SCM Manual Invoice  record (scon02}
09695
Internal memo. Free format memorandum for internal purposes. Completion is not mandatory
SCM Internal memo {scon01_inmemo}
09696
Memo. Free format memorandum for external purposes. Completion is not mandatory.
SCM Memo {scon01_exmemo}
3 automated processes
Calculation ext end (part of DEP after day roll).
Invoice order line creation (part of DEP after calc ext end).
Invoice creation (part of DEP after invoice order line creation)
Contract period
Start
End
Ext End
Logical rules
<end date
>start date
>end date
Format
date
date
Date
Who
User entry
User entry
System calc
Contract End and Extended End
The contract has a defined end date.
If a contract end date is not strictly defined but a function of the present date and notice period (if present) the logic is like this:
For invoicing the contract needs to set the rules for when an invoice needs to be created and what rules apply to the invoicing period


Invoice period set the period for invoice creation. Valid codes are SCC unit codes set as T(ime) type.
Method defines how the Invoice period is to be applied. Logically speaking this is Month, Week, Day
MONTH should be PERIOD.
What is definition  of tank occupied?

Was this helpful?
Thanks for your feedback