SAP R/3 форум ABAP консультантов
Russian ABAP Developer's Club

Home - FAQ - Search - Memberlist - Usergroups - Profile - Log in to check your private messages - Register - Log in - English
Blogs - Weblogs News

Проблемы LSMW и транзкация CT04



 
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> ABAP
View previous topic :: View next topic  
Author Message
sergiucz
Специалист
Специалист


Age: 41
Joined: 17 Feb 2012
Posts: 62

PostPosted: Mon May 14, 2012 12:56 pm    Post subject: Проблемы LSMW и транзкация CT04 Reply with quote

Добрый день господа абаперы.
У меня проблема при загрузке признаков через LSMW.
Через shdb эту транзакцию никак не проити . Я нашел по интернету что через ЛСМВ но проблемы пучком навалились .КТо сталкивался с такими проблемами отзовитесь! .

Помогите решить эту проблему.!
Заранее спосибо

_________________
Начинаюший ABAP-er
Back to top
View user's profile Send private message
Удав
Гуру
Гуру


Age: 48
Joined: 25 Jan 2008
Posts: 580
Location: Москва

PostPosted: Mon May 14, 2012 2:31 pm    Post subject: Reply with quote

См. ноту 213120 - Classification system: Batch input:
Quote:
As of Release 4.6A, the transactions of the class system are no longer suited for batch input.
If you have batch inputs from previous releases, you can continue using these since the old transactions still exist.
Where possible, use BAPIs or Direct Input instead of batch input. The old transactions will be eliminated in one of the future releases, so that the batch inputs will have to be converted anyway.
If you still want to use your own batch inputs, use the old transaction codes (such as CT01/02/03). If this should not work, use the alternatives mentioned above.
Furthermore, we recommend not to call those transactions using CALL TRANSACTION since unexpected problems may occur.

В общем, при batch input нужно использовать CT01 и CT02(изменение), а лучше вообще отказаться от него (см. ноту 373824 - Classification system: Programming interfaces

_________________
С уважением,
Удав.
Back to top
View user's profile Send private message
sergiucz
Специалист
Специалист


Age: 41
Joined: 17 Feb 2012
Posts: 62

PostPosted: Fri May 18, 2012 11:29 am    Post subject: Разобрался использовал LSMW и IDOC Reply with quote

Удав wrote:
См. ноту 213120 - Classification system: Batch input:
Quote:
As of Release 4.6A, the transactions of the class system are no longer suited for batch input.
If you have batch inputs from previous releases, you can continue using these since the old transactions still exist.
Where possible, use BAPIs or Direct Input instead of batch input. The old transactions will be eliminated in one of the future releases, so that the batch inputs will have to be converted anyway.
If you still want to use your own batch inputs, use the old transaction codes (such as CT01/02/03). If this should not work, use the alternatives mentioned above.
Furthermore, we recommend not to call those transactions using CALL TRANSACTION since unexpected problems may occur.

В общем, при batch input нужно использовать CT01 и CT02(изменение), а лучше вообще отказаться от него (см. ноту 373824 - Classification system: Programming interfaces



Спосибо за нотку!
Разобрался использовал LSMW и IDOC.
Были проблемы при создании нового партнера для iDoc. Но в конец разобрались.

_________________
Начинаюший ABAP-er
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Russian ABAP Developer's Club Forum Index -> ABAP All times are GMT + 4 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


All product names are trademarks of their respective companies. SAPNET.RU websites are in no way affiliated with SAP AG.
SAP, SAP R/3, R/3 software, mySAP, ABAP, BAPI, xApps, SAP NetWeaver and any other are registered trademarks of SAP AG.
Every effort is made to ensure content integrity. Use information on this site at your own risk.