Solution : https://service.sap.com/sap/support/notes/800918 (Connexion à SAP Service Marketplace requise)
Résumé :
Dans la gestion des spécifications SAP EH&S, l'utilisation de modules fonctionnels tels que C1F2_SUBSTANCES_READ, C1F2_SUBSTANCES_CREATE et C1F5_SPECIFICATIONS_READ peut entraîner une perte de données due à des initialisations inopinées de tampons. Pour atténuer cela, suivez attentivement la documentation de l'API, en particulier pour les intervalles d'enregistrements de données. Les nouvelles applications devraient préférer les modules C1F5_*, en utilisant C1F2_SUBSTANCES_SAVE_TO_DB pour les mises à jour de données des anciennes applications. Assurez-vous que les paramètres d'initialisation de la couche tampon sont correctement définis, y compris les dates clés et les numéros de changement. Les développeurs sont guidés pour gérer efficacement les couches de tampon afin d'éviter la perte ou la corruption des données. Toujours lancer la prochaine unité logique de travail après avoir enregistré dans la base de données.
Mots Clés :
init_data_old-valdat init_data_old-aennr init_data_old-further_settings-valfr init_data_old-further_settings-valtoboth, type-pool esp5 call function '<groupname>_admin' exporting i_action = 'init_info_get', #ec notext changing x_params = init_data_old, purely key date-related mode, _create/update/modify/delete modules, init_data_old type esp5_x_params_type, extensive interface conversions occur, internal reinitialization takes place, set boolean parameter i_flg_key_date_switch_only, possibly required change number
Notes associées :
| 1564132 | Authorization error for class type 100 is issued only once |
| 1559662 | Unclear message: "Entry in field &1 required" |
| 1556732 | (B)API may not report old characteristic values after lock |
| 1555822 | Creating several relationships in a (B)API call |
| 1537943 | Usage not displayed for restrictive authorizations |
| 1534533 | BAPI_BUS1077_GETLIST, error CX_SY_DYN_CALL_ILLEGAL_TYPE |
| 1526269 | EH&S Expert incorrectly displays an error |
| 1520381 | BAdI messages missing in C1F5_SPECIFICATIONS_READ |
| 1509009 | (B)API cannot generate sorting for identifiers |
| 1505911 | API changes referenced value assignments |
| 1494425 | Delete (B)API deletes inherited value assignment instances |
| 1490665 | Reading specifications takes a long time |
| 1484936 | Internal system error when copying specifications |
| 1463134 | Unnecessary conversion of characteristic vals from database |
| 1457612 | Meaningless status values displayed in scope of application |
| 1457528 | Empty RECNROOT fields for characteristics cause problems |
| 1439583 | BAPI_BUS1077_CREATE too slow for large amt of packaging data |
| 1439441 | BAPI msg "Invalid reference value in field &1" has no value |
| 1438416 | Specifying decimal places for concentrations for components |
| 1433872 | Slow processing with large no. of value assignment instances |
| 1430570 | Incorrect sort sequence when you create an instance |
| 1414058 | BAPI_BUS1077_CHANGE does not make any changes |
| 1411237 | Improvements in the specification API |
| 1388009 | Deleting regulatory lists deletes identifiers |
| 1379553 | Insufficient selection parameters for BAPI_BUS1077_GETLIST |
| 1376074 | Specification read API, combination inheritance & reference |
| 1352887 | BAPI_BUS1077_GETLIST outputs incorrect identifiers |
| 1335123 | Dialog error message when you submit a locked change number |
| 1321656 | Data inconsistency when value assgmt instance is inherited |
| 1320811 | Using the change BAPI to change long texts |
| 1301213 | Existence check for change numbers |
| 1292246 | Reading of packaging data with C1E7 cannot be deactivated |
| 1283732 | Error in read/delete API when several data records entered |
| 1279642 | Error in specification BAPI and API |
| 1274197 | Unnecessary locking conflict for inheritance relationships |
| 1258064 | Error in specification BAPI and specification API |
| 1247216 | Specification BAPI/API and inheritance: Important notes |
| 1232352 | API: Error during mass creation of specification data |
| 1180441 | Existing characteristic data is deleted |
| 1172118 | No error message for missing unit of measure "1" |
| 1171686 | API: Missing check for number of user-defined texts |
| 1155119 | Message "Data was saved" despite termination in exit |
| 1146662 | EHSS_SPEC_CHECKS, saving of status changes |
| 1133746 | Irrelevant lock error: Data record is in process |
| 1120922 | Too much specification data is deleted |
| 1113145 | BAPI creates value assignment instances despite char. errors |
| 1111161 | FAQs when you are working with specification BAPIs |
| 1108229 | Data origin during deletion in ALE |
| 1092703 | Read BAPI incorrectly counts field ATSRT |
| 1083802 | Old create API interface updates the long text incorrectly |
| 1074977 | Example programs for specification BAPIs |
| 1073773 | Change BAPI changes specification key |
| 1071008 | Sample code for AT_SAVE_CHECK of BAdI EHSS_SPEC_CHECKS |
| 1066991 | Read BAPI isses duplicate value assignment headers |
| 1066636 | Reading of time intervals with read (B)API |
| 1064873 | Read BAPI does not read all specification headers |
| 1064186 | Mess.: No values are available for the key specified |
| 1061176 | "Component assignment allowed" is ignored by BAPI |
| 1055358 | BAPI calls deliver old errors from previous calls |
| 1053525 | Characteristic values of class type <> 100 are not posted |
| 1042303 | Buffer error C$ 128 when deleting detail data with API |
| 1036247 | Change BAPI sends unrequired message for status entries |
| 1031669 | Evaluation of changes with SAP enhancement C1F20001 |
| 1021534 | Poor system performance with BAPI_BUS1077_CHANGE |
| 1019218 | Read API delivers no data in lock conflicts |
| 1017979 | Value assignment instance is not updated after change |
| 1004557 | C14K_CLSYS_VAR_GET does not return the current object |
| 1000251 | User-defined texts for UN-listed substance: Long txt missing |
| 990009 | System reads overwritten referenced value assignments |
| 987402 | Usages are output twice |
| 985629 | Can delete value assignment instance despite missing auth. |
| 985626 | Several vals. for dangerous goods regul. w/ "Copy Template" |
| 979495 | (B)API of the specifications creates duplicate usages |
| 968778 | BAdI EHSS_SPEC_CHECKS and enhancements C1F20001, C1F20100 |
| 953708 | Create BAPI does not create material assignments |
| 947829 | Characteristic values are lost with class types <> 100 |
| 946701 | Deleting restrictions with the Delete (B)API |
| 945416 | Delete (B)API requires too much runtime |
| 940765 | Write authorizations unnecessarily required in EH&S Expert |
| 922010 | Delete API in C1F5 does not delete status entries |
| 916095 | Deleting to 2 value assignment details w/ API w/ change numb |
| 914719 | Inheritance is not updated after the set of rules has run |
| 914550 | Value assignmt not updated after you change characteristics |
| 914169 | (B)API does not transfer rec split for detail to val assigmt |
| 899820 | No error messages during specification import |
| 898235 | Unnecessary warning parameters w/ read API of specifications |
| 883189 | Transferring source data + target data simultaneously to API |
| 880183 | Read API module in C1F2 returns exception INTERNAL_ERROR |
| 877708 | No status data record numbers in the API error table |
| 877514 | Usage filtering with the BAPI with empty validity area |
| 814293 | Data loss when you navigate between object types |
| 732628 | Blcks remain actve for unncssrly lng time with specfctn BAPI |