如何将数据导入SAP
作为 SAP 镇上的一个完全陌生的人，我想将我自己的应用程序（移动销售人员自动化）数据传输到 SAP。我的应用程序有客户、库存、库存、发票（和运单）、支票、付款、托收、库存转移数据等的记录。我有一个额外的数据库，用于保存记录的匹配。 IE。我的应用程序中 ID 为 345 的客户在 SAP 中拥有密钥 120-035-0223。当然，每条记录都必须知道它的对应记录，包括参数。
在 Google 和 SAP 帮助网站上搜索了一天后，我发现这比我预期的要痛苦一些。特别是 SAP 网站甚至没有给出任何线索。说我找不到。
我们将数据传输到其他一些 ERP 系统，其中一些需要 XML 文件，另一些则公开其 API。
我的观点是，Sql Server 的 SSIS 适合我吗？我希望如此，这样我就可以在自己的地盘上战斗了。由于客户的要求会有很大差异，因此我将灵活性视为最重要的标准。另外，我想传输尽可能多的数据。
任何帮助表示赞赏。
As a complete stranger in town of SAP, I want to transfer my own application's (mobile salesforce automation) data to SAP. My application has records of customers, stocks, inventory, invoices (and waybills), cheques, payments, collections, stock transfer data etc. I have an additional database which holds matchings of records. ie. A customer with ID 345 in my application has key 120-035-0223 in SAP. Every record, for sure, has to know it's counterpart, including parameters.
After searching Google and SAP help site for a day, I covered that it's going to be a bit more pain than I expected. Especially SAP site does not give even a clue on it. Say I couldn't find.
We transferred our data to some other ERP systems, some of which wanted XML files, some other exposed their APIs.
My point is, is Sql Server's SSIS an option for me? I hope it is, so I can fight on my own territory. Since client requests would vary a lot, I count flexibility as most important criteria. Also, I want to transfer as much data as I could.
Any help is appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我参与的过去十几次迁移中的一些建议：
不要尝试绕过 SAP 系统并直接导入 SAP 数据库。想都别想。如果出现任何问题，您就破坏了生产系统 - 并且您是受到指责的人。
决定您是需要迁移类型场景（单次传输）还是永久接口（每 n 分钟/小时/天传输一次）。这会产生巨大的差异（例如：在迁移场景中，您通常不必担心一遍又一遍地更新相同的记录 - 在永久界面中，您必须处理这个问题）。如果以后必须改变决定，通常必须从头开始。
找一个既了解所涉及的 SAP 模块又了解该模块在您的系统中的定制和使用方式的人员。您可能需要各种专家 - 一位对模块有深入了解的顾问和一位对实际数据输入和使用方式有详细了解的关键用户。
让自己熟悉所涉及的数据字典结构。您需要这些知识才能将输入数据正确映射到 SAP 结构。
询问专家是否有可用的接口。如果有，那么专家应该能够告诉您更多相关信息，包括文档。如果没有，您就必须自己创建一些东西。
对于迁移场景：与关键用户一起手动输入代表性记录，以确保您掌握了所有详细信息（哪些字段内容会转到 SAP 系统中的哪个位置？我们是否拥有所有所需的所有数据）领域？）。在许多情况下，您可以使用事务记录器 (SHDB) 来跟踪您输入的内容，尤其是技术字段名称。
查看旧系统迁移工作台 (LSMW) 。首先它可能看起来有点复杂，但它是一个用于多种用途的好工具。
一如既往，YMMV。哦，还有 - 准备好学习 ABAP。您至少应该能够阅读它，了解正在发生的事情并逐步执行调试器中的程序，否则事情会变得非常令人沮丧。
Some advice from the past dozen migrations or so I was involved in:
Do NOT try to bypass the SAP system and import into the SAP database directly. Don't even think of it. If anything goes wrong, you have shredded a production system - and you're the one who's getting the blame.
Decide whether you want a migration-type scenario (a single transfer) or a permanent interface (transfer every n minutes/hours/days). This makes a huge difference (for example: in migration scenarios you'll usually won't have to worry about updating the same record over and over again - in a permanent interface, you'll have to take care of this). If you have to change your decision later on, you'll usually have to start from scratch.
Get someone who knows both the SAP module involved and the way the module is customized and used in your system. You might need various experts - a consultant with in-depth knowledge of the module and a key user with detailed knowledge about the way the actual data is entered and used.
Make yourself familiar with the data dictionary structures involved. You'll need this knowledge to correctly map your input data to the SAP structures.
Ask the expert if there are any interfaces available. If there are, then the expert should be able to tell you more about it, including documentation. If there aren't any, you'll have to create something yourself.
For a migration scenarion: Perform a manual entry of representative records with a key user to make sure you have all of the details covered (Which field contents go where in the SAP system? Do we have all data for all of the required fields?). In many cases, you can use the transaction recorder (SHDB) to keep track of what you entered and especially of the technical field names.
Take a look at the Legacy Systems Migration Workbench (LSMW). It might seem a bit complicated first, but it's a great tool for many purposes.
As always, YMMV. Oh, and - be prepared to learn ABAP. You should at least be able to read it, understand what's going on and step through programs in the debugger, otherwise things will get very frustrating.
简而言之：不。
大多数 vwegert 观点都是有效的：
用于创建/更改/读取客户的是这些B API：
每个功能域（仓库、物料、合同、订单、发票、付款等）都有自己的 BAPI。此外，每个大型 SAP 商店都会滥用某些字段，因此您很可能必须根据客户调整这些调用。您的客户应该理解这一点并愿意（习惯）为此付费。
In short: no.
Most of vwegert points are valid:
The ones for creating/changing/reading customers are these B APIs:
Each functional domain (warehouse, material, contracts, orders, invoices, payments etc.) have their own BAPIs. Also, each big SAP shop abuses some fields so you will most likely have to adapt these calls per customer. Your customer should understand this and be willing (used) to pay for it.