|
Добрый день.
Я так понимаю речь идет об IDOC CREAMAS.
Почитайте ноту Note 125131 - Entry of user-defined fields in IDoc CREMAS:
Symptom
This note explains the procedure to enhance message type CREMAS by user-defined segments.This procedure also applies to fields which were only included in the IDoc in future releases.
Other terms
ALE, vendor, CREMAS
Reason and Prerequisites
*
Solution
1. Creating new segments for CREMAS:
Create a new segment (Transaction WEDI -> Development -> IDoc Segments) for every affected table (for example: LFA1, LFB1, LFM1, LFBK).
Attributes LFA1 -> min. number = 1, max. number = 1
Attributes LFB1, LFBK, LFM1 -> min. number = 1, max. number = 9999
2. ALE outbound processing:
Call up Transaction SE37 -> Function module MASTERIDOC_CREATE_CREMAS
(the segments are processed here)
You can use user exit CUSTOMER-FUNCTION '001' to fill your new segments.
3. ALE inbound processing:
Call up Transaction SE37 -> Function IDOC_INPUT_CREDITOR (up to Release 4.5) or
Function ERP_IDOC_INPUT_CREDITOR (as of Release 4.6)
-> FORM routine IDOC_POST
You can use user exit CUSTOMER-FUNCTION '001'.
Note that the user exit is called after the CALL Transaction.This is necessary because the new fields cannot be processed with our CALL Transaction.It would be the easiest to write your new fields - within the user exit - directly to the database. This is not a problem as long as it does not matter to you that checks (for example, against domain values) are carried out. But this should also not be a problem as long as you ensure that both in the source system and in the target system the same data is available. If you set one or several of your new fields as required fields, you must set it/them to optional entry for batch input.
For further questions, contact Consulting. Read Note 82176 or 79159 if you are an SAP Retail customer.
_________________
Лучше быть умным и иногда тупить, чем быть тупым и постоянно умничать!
|
Вход
Регистрация
FAQ пользователя
Поиск
