Solution : https://service.sap.com/sap/support/notes/539305 (Connexion à SAP Service Marketplace requise)
Mots Clés :
= visibilitymodldonly = modeled onlymethods level vis modldonly descriptionmethods type visib, typing reference type --------------------------------------------------------------------in_bdoc_type importing type smog_gnameret_use_in_queue returning, parameter type optional typing reference type -------------------------------------------------------------------queues exporting, parameter type optional typing reference type -------------------------------------------------------------------queues changing, modldonly description -------------------------------------------------------------------__use_in_queue static public check, field key initial values data element -----------------------------------------client, type optional ------------------------------------------------------------e_exploded_single_queues type smw3tt_bdq xchoose save, smw3inqnamprocstate char1upd_date updatupd_time uptimupd_user unamechoose save, data browser/table view maint field, manual implementation create database table smw3_bdocq
Notes associées :
| 765236 | FAQ: Queueing in CRM and R/3 |
| 763632 | Collective note for mass queue problems |
| 689038 | Analysis of mass queue behavior on the CRM server |
| 679039 | CSA_MASS_BUPA despite deactivated mass queues |
| 677800 | Problems in queue determination |
| 623195 | Flow-specific entries in the SMOFPARSFA table |
| 618823 | Problems when you implement note 539305 |
| 597608 | Queue determntn:initial load from CRM Server to R/3 Back End |
| 580487 | Guidelines for deactivating the mass queues CSA_MASS_BUPA |
| 568127 | Change of the mass queue handling for condition master data |
| 541407 | Mass queue causes performance problems |
| 529764 | Using inbound queues for CSA queues |