Ansicht
Dokumentation

CPF2960 - Field &4 will not map from file &1 in &2. ( OS/400 )

CPF2960 - Field &4 will not map from file &1 in &2. ( OS/400 )

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by IBM.
SAP E-Book


Message : CPF2960
Field &4 will not map from file &1 in &2.

Message Long Text :

Cause . . . . . : Both the from-file &1 in library &2 and the to-file &5 in library &6 have a field with the same name &4, but the attributes are incompatible. The field cannot be mapped because of reason &8. The following are the reasons:
1 -- The field is a character, DBCS (Double-Byte Character Set), Binary Character, or UCS-2 (Universal Coded Character Set), UTF-8 (UCS Transformation Format) -character, or UTF-16-graphic field in one of the files and a numeric field in the other.
2 -- The to-file field is a DBCS-only or a DBCS-graphic field and the from-file field is a fixed length character or DBCS-open field with an odd byte length.
3 -- The field is a date field in one of the files and NOT a date, character, zoned, or packed field in the other file with a compatible length. The length required for character, zoned, and packed fields is based on the current job's DATFMT without separators, and must be valid for the expected date form of the field. See the Database file management topic collection in the Database category in the IBM i Information Center book, http://www.ibm.com/systems/i/infocenter/, for specific field attributes required when copying date fields from or to character, zoned, or packed fields.
4 -- The field is a time field in one of the files and NOT a time, character (with minimum length 4 if its the from-file field or minimum length 8 if its the to-file field), or zoned decimal (with length 6,0) field in the other file.
5 -- The field is a timestamp field in one of the files and NOT a timestamp, character (with minimum length 14), or zoned decimal (with length 14,0) field in the other file.
6 -- There is not a valid conversion from the from-file field CCSID (Coded Character Set Identifier) to the to-file field CCSID.
7 -- The field is a binary field with decimal position greater than 0 in one of the files and NOT a binary field with the same decimal position in the other file.
8 -- The field is a DBCS-graphic field in one of the files and a character field in the other.
9 -- The field is a UCS-2-graphic field in one of the files and a character, DBCS-open, DBCS-either, or DBCS-only field, with CCSID(65535) in the other file.
Recovery . . . : Specify FMTOPT(*NOCHK) to bypass mapping, and then try the request again.
Technical description . . . . . . . . :
-- Only fields with compatible attributes can be mapped. See the Database file management topic collection in the Database category in the IBM i Information Center book, http://www.ibm.com/systems/i/infocenter/, for more information on the CPYF and CPYFRMQRYF commands and what field attributes are required. Also see CPD2961.

Message File : QCPFMSG
Library Message File : QSYS2924


RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by IBM.

Length: 3245 Date: 20240425 Time: 191213     sap01-206 ( 3 ms )