How to Create Jinshui Information in Account Receivable

Purpose of Document

This document is to explain what the contents of Jinshui/JinShui files are which have been created through China Localization Code in EnterpriseOne. Currently EDI interface between tax authority and JDE is required in reporting tax in China.

According to China localization package, after invoice printing R42565/R03B505 - Print Invoices with 'Localization Country Code' "CN - China", F75C001 - Chinese GUI cross reference file is populated, and it's saying P007101 - Text File Processor to create/generate flat file for Jinshui Interface.

Also that documentation states that Inbound Jinshui Interface file can be uploaded back to JDE through P007101 text processor and R75C7101 - Download JinShui return file into J.D. Edwards - China - 75C.

Disclaimer: Since the request can be varied per JinShui version so the mapping can be changed without having prior notice

Note: Oracle's JDEdwards may meet requirement suggested by Tax Authorities in China but actual format of data suggested by Tax Authority can be vary. In case as-is format/contents does not meet your legal/legislative requirement, please contact Global Customer Care because Oracle is policy taker rather than policy giver

Note: JinShui can be described as VAT Golden Tax System (JinShui). It is required by the tax bureau/authorities that the actual invoice issued to customer should be printed and payable tax amount generated through taxation control system. After the invoice is processed by Golden Tax system, the invoice number
assigned by Golden Tax System would be written back to the corresponding invoice record in
JDE EnterpriseOne system, for the data tracking purpose.



If you are calling JinShui interface through R42565 - Print Invoice, please refer <> E1: 75C: How to Create Jinshui Information in Sales Order

What is the repository for Text String?

Note: Above tables are repository for any type of transaction. That is, it is not specific to China Localization


What is the sequence of transaction in relation with JinShui text file(for EDI) creation?


  1. R03B505 - Print Invoice/(A/R) Print Invoice: to call Localization Code of N7000550 and N7000551
    1. N7000550 - R03B505PrintARInvoices (R03B505 - Print A/R Invoice): To hand over parameters based on F03B11
    2. N7000551 - R03B505PrintARInvoice (R03B505 - Process Localization Requirements) which is calling N75C03B1 - Create Chinese GUI interface file from A/R in following sequence (Read Processing Option template values of R75C03B1)
      1. N75C03B1 - ProcessGUIHeader (Process GUI Invoice Header) create cache to make use of in writing header and detail
      2. N75C03B1 - WriteGUIHeader (Write GUI Invoice Header) to write GUI invoice header
      3. N75C03B1 - WriteGUIDetail (Write GUI Invoice Detail) to write detail data
      4. N75C03B1 - EraseCache (Erase Cache) to delete all the caches created during process
    3. Return to N7000551
    4. Return to N7000550
  2. Return to calling UBE R03B505
Note: Localization code will be updated through Plug & Play so if the ESU contains any special instruction, apply it with care


Where does some of the dynamic information come from?

It is coming from processing option of R75C03B1 - Create Chinese GUI interface file from A/R. Actual parameter is defined as below,

Parameter
 Value
 Member ID
 Size
1. Print Invoice Type
 Blank = JinShui interface and JDE File
1 = JDE Standard Invoice only
 cPrintJDEInvoice
 1
2. Invoice Remarks
szRemarks
 30
3. Line Item Unit of Measure
szUnitOfMeasureAsInput
 2
4. Line Item Quantity
mnUnitsQuantityShipped
 15
5. Line Item Category Value (Required)
szItemGroup05
 6
6. Item Description (Required)
szItemDescription
 30
7. Item Specification
szItemSpecification
 15
8. Checked By
mnCheckedBy
 8
9. Received By
mnReceivedBy
 8
10. Sales Detail String
szSalesDetail
 3
11. Header Note String
szHeaderNotes
 3
12. Header Document Name
szHeaderDocName
 3
13. Enter the Bank Transit Record Type
     Default: "G"
cBankTransitRecordType
 1


Note:



How the JinShui Header File gets created?

Seq
 String Value
 Format
 Size
 Source of Data
1
 Virtual Invoice Number
8
 NN(75|1)
2
 Number of detail lines (rows)
3
 Total Number of rows for detail
3
 Customer Name
40
 F0101.ALPH (WHERE AN8 = mnCustomerNumber)
4
 Customer Tax ID
15
 F0101.TAX
5
 Customer Address and Phone Number
80
 F0116.ADD1 + ADD2 + F0115.AR1 + PH1
6
 Customer Bank Name and Account
80
 F0030.DL01 (WHERE BKTP='X' and AN8=mnCustomerNumber)
+ F0030.CBNK
7
 Remarks
160
 (To be implemented)
8
 Name for POCheckedBy
 PO Value
 30
 Processing Option value in R75C03B1|Version
9
 Name for POReceivedBy
 PO Value
 40
 F0101.ALPH (for address number of PO CheckBy in Processing Option)
10
 Sales Detail
60
 evt_szSalesDetailString_PDSC (Processing Option of R75C03B1)
11
 Invoice Date
 EMD format
 8
 F03B11.DIVJ
12
 Company Bank Name and Account
50
 F0030.DL01 + F0030.CBNK
13
 Company Address and Phone
80
 Ref #1

Note:
EMD format: Based on date mask E - 4 digit year, M - 0 padded 2 digit month, D - 0 padded 2 digit day

Ref #1
1. Get F0115.PH1 and AR1 based on F0010.AN8 where F0010.CO = F03B11.KCO
2. Get F0116.ADD1, ADD2, ADD3, ADD4 based on F0116.AN8 = F0010.AN8 where F0010.CO=F03B11.KCO
3. Strip all the blank and add A Space betweens value computed from 1 and 2
4. Compute the length of each values
5. If total length of ADD1 + ADD2 + ADD3 + ADD4 + AR1 + PH1 is longer than 80 characters then set output without having AR1 + PH1


How JinShui Detail File gets created through NER N75C03B1?

Seq
 String Value
 Format
 Size
 Source of Data
1
 Item Description
 Check PO Value
 30
 POItemDescriptionDefault OR szDescriptionRemark which is F03B11.RMK
2
 Unit of Measure
 Check PO Value
 3
 Processing Option value of R75C03B1
3
 Specification
 Check Po Value
 15
 POItemSpecification OR F03B11.SFX
4
 Quantity
15
 POQuantity
5
 Amount
15
 F03B11.ACR - F03B11.CTAM
6
 Tax Rate
4
 F4008.TXR1 + TXR2 + TXR3 + TXR4 + TXR5 for specific Tax Area
7
 Category Code
 PO Value
 6
 Processing Option value of R75C03B1
8
 Discount
15
 F03B11.ADSC
9
 Tax Amount
15
 F03B11.STAM
10
 Discount Tax Amount
15
 evt_mnTaxAmount / evt_mnDiscountRate
11
 Discount Rate
15
 (to be implemented)
12
 Unit Price
15
 0 (hard coded)
13
 Price Method
1
 0 (hard coded)

What are other considerations?


Are there any cross reference file which stored the text file which N75C03B1 create?

Yes the table F75C001 - Chinese GUI cross reference file will contain these information including GUI Number
Column of F75C001
 JinShui
 Reference
DOC0 - Document
 Document Number in Header File
LINN - Line Number
 Line Number in Detail File
DOC - Document (Voucher, Invoice, etc.)
 F03B11.DOC
DCT - Document Type
 F03B11.DCT
KCO - Document Company
 F03B11.KCO
SFX
 F03B11.SFX
DOCO - Document (Order No, Invoice, etc.)

DCTO - Order Type

KCOO - Order Company (Order Number)

GUI

AEXP - Amount - Extended Price
 Amount in Detail File
CRR - Currency Conversion Rate - Spot Rate
 F03B11.CRR
CRCD - Currency Code - From
 F03B11.CRCD
CRDC - Currency Code - To
 F03B11.CRDC
RCDS

USER - User ID
 SL UserID
PID - Program ID
 SL ReportName
UPMJ - Date - Updated

UPMT - Time - Last Updated

JOBN - Work Station ID

IVD - Date - Invoice

DIVJ
 F03B11.DIVJ
CBNK - Bank Account Number - Customer
 evt_szCoBankAcctNo_CBNK
DL01 - Description
 evt_szCoBankName_DL01
UPRC - Amount - Price per Unit

AR1 - Phone Prefix
 evt_CoPhoneAreaCode_AR1
PH1 - Phone Number
 evt_PhoneNumberCo_PH1
ADD1 - Address Line 1
 evt_szCoAddressLine_DS80
C75STCI


Note:
Table Data Structure may be changed without having prior notice
Mapping can be changed to accommodate requirement from JinShui

Is there any reference in Chinese?

Refer attached files <" title="JinShui Format in Chinese">JinShui_Format.pdf> and <JinShui_Format_in_English.xls>


Note: If given information does not meet requirement of your local tax authorities, please contact Oracle's Global Customer Support with requested format of your local authorities