• A Confluence está sendo executada atualmente com todos os plugins que não são do sistema desabilitados. Pode haver perda de algumas funcionalidades
Linha Microsiga Protheus - Inglês

Páginas filhas
  • Accounts Payable Clearing - FINA340 - Financials - P12

Note

This routine was adjusted to comply with the General Personal Data Protection Law (LGPD law No. 13.70), so that some fields containing data regarded as sensitive and/or personal are blurred, becoming illegible.

01. OVERVIEW

This routine clears all advances made and registered by the Suppliers (PA bills type), in addition to the credit notes to be deducted (NDF bills type).

The advances selected and entered by the user are deducted from the total amount of the original bill.

02. EXECUTION

  • Manually

Procedure manually performed through routine Accounts Payable Clearing (FINA340), with the display of the screens involved in the process - actions/commands from the user are required

  • Automatically

Procedure automatically performed in routine Accounts Payable Clearing (FINA340) without the display of screen - no interaction from the user required.

Used in customizations in which the process does not required user's interactions (MSEXECAUTO)


Example of Automatic Routine 
#INCLUDE "Protheus.ch"
#INCLUDE "RWMAKE.CH"
#INCLUDE "TBICONN.CH"

Static __COMPAUT := Nil

User Function CMPAUTOMA()
	Local lRet := .F.
	Local cQry := ""
	Local aTipos := {"NF ", "PA ", "NDF"}
	Local cTblTmp := ""
	Local aNF := {}
	Local aPA_NDF := {}
	Local aContabil := {}
	Local bBlock := Nil
	Local aEstorno := {}
	Local nSldComp := 0
	Local nTaxaPA := 0
	Local nTaxaNF := 0
	Local nHdl := 0
	Local nOperacao := 0

	If __COMPAUT == Nil
		cQry := "SELECT E2_TIPO TIPO, R_E_C_N_O_ R_E_C_N_O FROM " + RetSqlName("SE2") + " "
		cQry += "WHERE E2_SALDO > 0 AND E2_TIPO IN (?) "
		cQry += "ORDER BY E2_TIPO" 
		cQry := ChangeQuery(cQry)
	__COMPAUT := FWPreparedStatement():New(cQry)
	EndIf

	__COMPAUT:SetIn(1, aTipos)
	cQry := __COMPAUT:GetFixQuery()
	cTblTmp := MpSysOpenQuery(cQry)

	While (cTblTmp)->(!Eof())
		If (cTblTmp)->TIPO $ MVPAGANT+"|"+MV_CPNEG
			Aadd(aPA_NDF, (cTblTmp)->R_E_C_N_O) 
		Else
			Aadd(aNF, (cTblTmp)->R_E_C_N_O)
		EndIf 

		(cTblTmp)->(DbSkip()) 
		lRet := .T.
	EndDo 

	(cTblTmp)->(DbCloseArea())
	cTblTmp := ""

	If lRet
		Pergunte("AFI340", .F.)
		lContabiliza := MV_PAR11 == 1
		lAglutina := MV_PAR08 == 1
		lDigita := MV_PAR09 == 1

		lRet := FinCmpAut(aNF, aPA_NDF, aContabil, bBlock, aEstorno, nSldComp, dDatabase, nTaxaPA ,nTaxaNF, nHdl, nOperacao)

		If lRet
			Alert("Compensation successful")
		Else
			Alert("An error occurred in the compensation process")
		EndIf
	EndIf
	
Return

Note

To use the Automatic Accounts Payable Clearing process, call the function: FinCmpAut. Clearing can be carried out from N to N: N advances/returns (PA or NDF) for N bills (NF, DP, etc.) or vice versa.

Automatic Accounts Payable Clearing


03. OPERATIONS

  • Clear

Use this operation to clear bills payable:

 - Clearing bills from a supplier/store with advances from the same supplier/store

 - Clearing bills from a given supplier with advances from the same supplier regardless of the bill receivable store

 - Clear a bill from a given supplier with advances from several suppliers, in which case a supplier range or all suppliers can be established. Then, the bill can be cleared with any advance bill from the same supplier pending in the bill file, irrespective of the supplier for this bill.


Important

The Clearing Date must be after the date of issue of the bills involved. For example:

  • PA issued on 3/29
  • NF issued on 4/02

You can only clear these bills after 4/02, considering that on 3/29 the NF did not yet exist, so the postings concept is correctly applied to clearing operations. (E2_Posting after E2_ISSUE)

  • You cannot, through Financials, clear Advance Payments bound to Purchase Orders.

For clearance between advances and bills from different branches, use button Branches to define which branches to consider for selection of bills to clear.If you do not use button Branches, only bills of the current branch are considered for clearing.

Note

If the financial base is fully shared and you do not use button Branches, all advances from all branches are considered for the process.


  • Delete

Operation to delete the transaction generated by the clearing

  • Reversal 

Operation that allows reversing the transaction generated by clearing, thus generating its counterpart.

  • Caption

It displays the caption chart and meanings related to bill payable status.

  • Search

Search for the bill in the accounts payable file, having it placed and highlighted in the browser.

  • View

Operation to view the bill selected and check its balance and value.

04. PARAMETERS APPLIED

List of parameters applied to FINA340 and its processing


05. ACCOUNTING

The booking of processes applied to an accounts payable clearing via Financials module is done through the standard entries below:

SE

Taxable Event

ON

OFF (CTBAFIN)

589

Cancellation of clearing of accounts payable bills

X

X

597

Clearing of accounts payable 

X

X


IMPORTANT!

The booking of clearing will always be made based on the data of the Cleared Bill and it can be any type of obligation: NF, TX, DP, etc. as long as the transfer (SE5) has the following classification: E5_TIPODOC = 'CP' and E5_MOTBX = 'CMP'

Booking Variables

Information

Booking of DIC type

The booking of DIC type generated by clearing can be done by LP 510 - Addition of Bill Payable, because it is generated through the FINA050 (Accounts Payable) automatic routine.


Booking of taxes generated when clearing.

LP 597 - Clearing Payable itself can book taxes generated by clearing, through variables: NPIS340, NCOF340, NCSL340, NIRF340, NISS340.


See Also:

Booking of CR/CP Clearings

06. TABLES

  • SE2 - Accounts Payable Register 
  • SE5 - Checks Register 
  • SED - Natures Register
  • SA2 - Suppliers Register
  • FK2 - Postings Payable
  • FK3 - Calculated Taxes
  • FK4 - Withheld Taxes
  • FK5 - Bank Transactions
  • FK6 - Accessory Values
  • FK7 - Auxiliary Table  
  • FKA - Transaction Tracking


07. ENTRY POINTS

Entry point

Note

F340BROW

Entry point F340BROW is called before the browser, which you can use to handle the data displayed by the browser.
Document: http://tdn.totvs.com/x/56Jc

F340LIBT

The entry point indicates whether to validate the bill release when clearing.
Document: http://tdn.totvs.com/x/_a2FDg

F340DTFIN

PE is called in MV_DATAFIN parameter validations found in CP Clearing.
Document: http://tdn.totvs.com/x/6qJc

F340TAXA

In this entry point you can change the currency rates used when clearing accounts payable.
Document: http://tdn.totvs.com/x/aK_FDg 

F340ATLIS

Use this entry point to handle the aTitulos Array, to change the listBox of the clearing screen.Document: http://tdn.totvs.com/x/gKRc

F340TOTCP

 Use entry point F340TOTCP() to handle the total values of bills to be cleared.
Document: http://tdn.totvs.com/x/nYIbCQ

F340MKTIT

Use entry point F340MKTIT to customize bills already selected in the markbrowse. You can handle an array that contains the bills and, with its 8th occurrence, containing a logical value that indicates whether the bill is selected or not.Document: http://tdn.totvs.com/x/L6Rc

F340NAT


F340_PA

Entry point F340_PA is executed after booking each clearance payable bill.
Document: http://tdn.totvs.com/x/7aJc

F340SE5

Entry point F340SE5 handles Processed Bank Transactions with parameter Recno of records SE5 used in Clearing.
Document: http://tdn.totvs.com/x/sAKqC

F340GRV

Entry point F340GRV validates the addition in routine Accounts Payable Clearing (FINA340)
Document: http://tdn.totvs.com/x/IgBzB

F340ACAN

Use this entry point to create a rule to enter when the Reversal will occur, or not.
Document: http://tdn.totvs.com/x/j7GFDg

F340CAN

Entry Point called upon confirmation of clearance reversal.
Document: http://tdn.totvs.com/x/zoFdAg

F340GREST

Recording of additional data in clearance reversal
Document: http://tdn.totvs.com/x/iqVc

F340FCAN

Use this entry point to save complementary data when reversing the clearance.
Document: http://tdn.totvs.com/x/W7KFDg

FA340QRY

Query complement for cancellation of clearance
Document: http://tdn.totvs.com/x/lgwGD

FA340FILT

Run entry point FA340FILT when assembling the table of bills to clear and use it to select which bills you will clearDocument: http://tdn.totvs.com/x/rqNc

F340CMP

Use this entry point to calculate the NDF or PA bill. It is called in function Fa340Tit()
Document: http://tdn.totvs.com/x/6aJc

FA340ORD

Use this Entry Point to edit the index, changing the order of bills displayed on the markbrowse for clearing payableDocument: http://tdn.totvs.com/x/r6Nc

F340ValOk

Entry point F340ValOk allows controlling data and confirming the payable bills clearing screenDocument: http://tdn.totvs.com/x/fKVc

F340TOTCP

Use this entry point to handle the total values of bills to be cleared.
Document: http://tdn.totvs.com/x/nYIbCQ

F340VLD

Use this entry point to validate whether a bill will be cleared or not.Document: http://tdn.totvs.com/x/J6Vc

F340LEGE


SE5FI340

Use this Entry Point to make complementary recordings in table SE5, after recording the bank transaction of the main bill in automatic clearing payableDocument: http://tdn.totvs.com/x/56Rc

SE5FI341

Use this Entry Point to make complementary recordings in table SE5, after recording the bank transaction of the Advance bill in automatic clearing payable.Document: http://tdn.totvs.com/x/6KRc

F340GERNDF

Use this to save additional fields when adding the NDF generated by the clearing payable.
Document: http://tdn.totvs.com/x/kvdbDQ

FA340NDFGrv


F340FLCP

Use this to implement a complementary expression in the bills filter.
Document: http://tdn.totvs.com/x/66Jc

F340FCPTOP

Use this entry point to create a new filter for the routine  Accounts Payable Clearing - FINA340. 
Document: http://tdn.totvs.com/x/r_xZE


08. OTHER CLEARING RULES


09. MORE INFORMATION


NOTITSEL in reversal of clearing

Upon opening the wizard NOTITSEL in reversal of clearing, validate field E5_FILORIG in clearing records and also check fields of key (Prefix+number+installment+type+supplier+store) of tables SE2 and SE5. Fields must have corresponding sizes in both tables.