SAP ABAP JSON - Revision history

WikiSysop: /* leer tags dinámicamente */

2025-10-16T00:06:46Z

leer tags dinámicamente

WikiSysop: /* leer tags dinámicamente */

2025-10-15T23:27:24Z

leer tags dinámicamente

WikiSysop at 23:26, 15 October 2025

2025-10-15T23:26:56Z

WikiSysop: /* USO DE TIPO BOOL */

2025-10-03T21:47:13Z

USO DE TIPO BOOL

WikiSysop at 21:46, 3 October 2025

2025-10-03T21:46:33Z

WikiSysop: /* Ejemplo Serializing JSON */

2025-10-03T21:41:56Z

Ejemplo Serializing JSON

WikiSysop: /* Ejemplo Serializing JSON */

2025-10-03T21:41:12Z

Ejemplo Serializing JSON

WikiSysop at 16:08, 14 October 2020

2020-10-14T16:08:25Z

WikiSysop: /* Uso en programas ABAP (XSLT) */

2020-08-26T18:34:45Z

Uso en programas ABAP (XSLT)

WikiSysop: /* Uso en programas ABAP */

2020-08-26T18:34:10Z

Uso en programas ABAP

@@ Line 444: / Line 444: @@
 }</nowiki>
-queremos leer IdDocumento Url Guid, tenemos:
+y queremos leer IdDocumento Url Guid, tenemos:
   <nowiki>

@@ Line 446: / Line 446: @@
 queremos leer IdDocumento Url Guid, tenemos:
-<nowiki>
+ <nowiki>
 FORM get_json_data USING iv_response_json TYPE string
                  CHANGING ev_iddocumento TYPE i

← Older revision		Revision as of 23:26, 15 October 2025
Line 407:		Line 407:
	"overwrite":true		"overwrite":true

		+	==leer tags dinámicamente==
		+	Por ejemplo si tenemos el siguiente JSON
		+	<nowiki>
		+	{
		+	"Code": 0,
		+	"Message": "OK",
		+	"Document": {
		+	"IdDocumento": 282476,
		+	"IdTipoDocumento": 437,
		+	"Titulo": "pablo.pdf",
		+	"Url": "http://www.misitio.com/sites/SAP/teletrabajo/DESA/pablo.pdf",
		+	"Guid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
		+	"IdArchivo": null,
		+	"IdPfe": null,
		+	"HashCode": "P7R77Vy9N6JOXXXXXXXXXX==",
		+	"Archivo": null,
		+	"Metadata": {
		+	"Format": {
		+	"Mimetype": "application/pdf"
		+	},
		+	"Identifier": {
		+	"Uri": "http://www.misitio.com/sites/SAP/teletrabajo/DESA/pablo.pdf",
		+	"Corfo": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
		+	"OriginalHash": "P7R77Vy9N6JOXXXXXXXXXX==",
		+	"Region": "RM"
		+	},
		+	"Date": {
		+	"Created": "2025-10-14 16:29:45"
		+	},
		+	"Creator": "Ingreso%20de%20Actas",
		+	"Type": "ANTECEDENTE TELETRABAJO",
		+	"Title": "pablo.pdf"
		+	},
		+	"Migrado": false
		+	}
		+	}</nowiki>

		+	queremos leer IdDocumento Url Guid, tenemos:
		+
		+	<nowiki>
		+	FORM get_json_data USING iv_response_json TYPE string
		+	CHANGING ev_iddocumento TYPE i
		+	ev_url TYPE string
		+	ev_guid TYPE string.
		+
		+	DATA: lr_data TYPE REF TO data.
		+	DATA: lo_data TYPE REF TO /ui2/cl_data_access.
		+	DATA: lv_guid TYPE string,
		+	lv_iddocumento TYPE i,
		+	lv_url TYPE string.
		+
		+	DATA: lr_sdescr TYPE REF TO cl_abap_structdescr.
		+
		+	lr_data = /ui2/cl_json=>generate( json = iv_response_json
		+	pretty_name = /ui2/cl_json=>pretty_mode-low_case ).
		+	CHECK lr_data IS BOUND.
		+
		+	lo_data = /ui2/cl_data_access=>create( ir_data = lr_data iv_component = 'Document-Guid' ).
		+	lo_data->value( IMPORTING ev_data = ev_guid ).
		+
		+	lo_data = /ui2/cl_data_access=>create( ir_data = lr_data iv_component = 'Document-IdDocumento' ).
		+	lo_data->value( IMPORTING ev_data = ev_iddocumento ).
		+
		+	lo_data = /ui2/cl_data_access=>create( ir_data = lr_data iv_component = 'Document-Url' ).
		+	lo_data->value( IMPORTING ev_data = ev_url ).
		+
		+	ENDFORM.</nowiki>

	[[Category:ABAP]]		[[Category:ABAP]]

@@ Line 404: / Line 404: @@
 en la serialización con /ui2/cl_json=>serialize la salida será del tipo:
-  "overwrite": false
+  "overwrite":false
 [[Category:ABAP]]

@@ Line 398: / Line 398: @@
 REPLACE ALL OCCURRENCES OF '\/' IN c_string WITH '/'.
 REPLACE ALL OCCURRENCES OF '\\' IN c_string WITH '\'.</nowiki>
 [[Category:ABAP]]

@@ Line 142: / Line 142: @@
 {"$schema":"sss","@odata.context":"odata","VeeeeryyyyyLooooongJSONAttrbuuuuuuuuuteeeeeeeeeee":"ssssname","STANDARD":"stan"}</nowiki>
   <nowiki>
    DATA lt_mapping TYPE /ui2/cl_json=>name_mappings.

← Older revision		Revision as of 21:41, 3 October 2025
Line 142:		Line 142:
	{"$schema":"sss","@odata.context":"odata","VeeeeryyyyyLooooongJSONAttrbuuuuuuuuuteeeeeeeeeee":"ssssname","STANDARD":"stan"}</nowiki>		{"$schema":"sss","@odata.context":"odata","VeeeeryyyyyLooooongJSONAttrbuuuuuuuuuteeeeeeeeeee":"ssssname","STANDARD":"stan"}</nowiki>

		+	<nowiki>
		+	DATA lt_mapping TYPE /ui2/cl_json=>name_mappings.
		+
		+	lt_mapping = VALUE #( ( abap = `FOLDERPATH` json = `folderpath` )
		+	( abap = `FILENAME` json = `filename` )
		+	( abap = `BASE64FILE` json = `base64file` )
		+	( abap = `IDTIPODOCUMENTO` json = `idTipoDocumento` )
		+	( abap = `METADATA` json = `metadata` )
		+	( abap = `OVERWRITE` json = `overwrite` )
		+	( abap = `CREATOR` json = `Creator` )
		+	( abap = `DESCRIPTION` json = `Description` )
		+	( abap = `ABSTRACT` json = `Abstract` )
		+	( abap = `FUNCIONARIO` json = `Funcionario` )
		+	( abap = `MES` json = `Mes` )
		+	( abap = `AÑO` json = `Año` )
		+	).
		+	ev_json_string = /ui2/cl_json=>serialize( data = is_createdocument " Data to serialize
		+	pretty_name = /ui2/cl_json=>pretty_mode-low_case
		+	name_mappings = lt_mapping ).</nowiki>
	* Clase CL_FDT_JSON		* Clase CL_FDT_JSON

@@ Line 141: / Line 141: @@
 {"NOMBRE":"Deadpool","EDAD":1000,"NACIMIENTO":"1972-09-15","DIRECCION":"USA","PLATA":999999}
 {"$schema":"sss","@odata.context":"odata","VeeeeryyyyyLooooongJSONAttrbuuuuuuuuuteeeeeeeeeee":"ssssname","STANDARD":"stan"}</nowiki>
 ==Ejemplo de programa que genera archivo XSLT JSON, útil para Json con muchos campos==

@@ Line 21: / Line 21: @@
    json = json_writer->get_output( ).
    PERFORM decode USING json
                CHANGING p_string_json.

@@ Line 1: / Line 1: @@
 ==[[SAP_ABAP_JSON_XSLT|Ejemplo XSLT JSON]]==
-==Uso en programas ABAP==
+==Uso en programas ABAP (XSLT)==
   <nowiki>FORM crear_json USING p_guia TYPE zhr01_dgtl
                        p_uname