Páginas filhas
  • Type B (MATA360 - SIGACOM)

Versões comparadas

Chave

  • Esta linha foi adicionada.
  • Esta linha foi removida.
  • A formatação mudou.

Incluir Página
Type B (MATA360 - SIGAFIN)
Type B (MATA360 - SIGAFIN)

This type of term enables the combination of several types of due dates (type: 1 to 8, except type 9) in a single payment term.

In the window for adding payment term, the upper part displays the fields to define the existing types of payment terms; the lower part displays the rows to define the items when the term is type B. In this case, only the fields defined in the items are considered to calculate the due dates of trade notes.

The items of the payment term type B are stored in the table Payment Term Split - SEC.

Parameters Used

  • MV_AGLDUPB - It defines if trade notes with the same due date must be grouped.
  • MV_DATDUPB - It indicates if, to calculate due date, it will apply the date of the last bill generated as reference for the next term (1=Update) or the initial date will be always used (2=Initial).

Examples of Usage

Example 1

Parameters MV_AGLDUPB = 2 (Do not Group) and MV_DATDUPB = 1 (Update)

...

Code

...

001

...

Type

...

B

...

Payment Term

...

0 (the system does not consider this information since it is type B, but, as it is a required field, some value must be typed in)

...

Description

...

Multiple Conditions

...

Item

...

Type

...

Paym.Term

...

Apportionment

...

01

...

3

...

3,30,7

...

50%

...

02

...

1

...

00,15

...

50%

...

Reference Date

...

12/15/03

...

Bill Amount

...

1000.00

...

Bills Generated

...

2/7/04

...

166.67

...

3/7/04

...

166.67

...

4/7/04

...

166.67

...

4/7/04

...

250.00

...

4/22/04

...

250.00

Parameters: MV_AGLDUPB = 1 (Group) and MV_DATDUPB = 1 (Update), the bills will be generated as it follows:

...

Bills Generated

...

2/7/04

...

166.67

...

3/7/04

...

166.67

...

4/7/04

...

416.66

...

4/22/04

...

250.00

Parameter MV_DATDUPB = 2 (Initial), the bills are generated as follows:

...

Bills Generated

...

2/7/04

...

166.67

...

3/7/04

...

166.67

...

4/7/04

...

166.67

...

12/15/03

...

250.00

...

12/30/03

...

250.00

Example 2

...

Code

...

021

...

Type

...

B

...

Payment Term

...

0 (the system does not consider this information since it is type B, but, as it is a required field, some value must be typed in)

...

Description

...

Multiple Conditions

...

Item

...

Type

...

Paym.Term

...

Apportionment

...

01

...

1

...

0.30

...

50%

...

02

...

1

...

0.60

...

50%

...

Reference Date

...

10/1/03

...

 

...

Bill Amount

...

100.00

...

 

...

Bills Generated

...

10/1/03

...

25.00

...

10/31/03

...

25.00

...

10/31/03

...

25.00

...

12/30/03

...

25.00

If the parameter MV_AGLDUPB is set to group, the bills will be generated as follows:

...

Bills Generated

...

10/1/03

...

25.00

...

10/31/03

...

50.00

...

12/30/03

...