BAPI and RFC are not the same level concept, can't say that the BAPI function and the RFC function are considered to be inevitable and distinguished from the literal. For example, ask a question: You can be divided into which category, answer: men and old people, oh ~~, everyone knows, men are based on gender, old people are age. BAPI is a function-based function based on SAP. The key is that they have processed the business objects of R / 3, such as document sales orders, organization: company, etc., they are a series of entities. RFC is a way in which a man may also be an old man. A BAPI function can often be an RFC function (I don't know if all BAPI can have RFC technology to call, But at least most of them, with BAPI in VB, because this BAPI function has RFC features)
BAPI
Is
SAP
A good idea, and the business object is object. Just learn
ABAP / 4
When you don't understand
SAP
Said
"ABAP /
4 "
middle
'
4 '
Instead, it is more like a scripting language, and the top is more
C
Like, but since I came into contact
BAPI
After that, I realized
SAP
Say
ABAP
Be a kind
4G
The language is indeed inevitable.
When calling outside
BAPI
When it is
VB
You can
SAP
Such as orders, materials, employees, factories, etc. are treated as an object, and this treatment is then so simple, and it may be possible, the most critical is:
1.
collect
BAPI
Data required by the function
,
That is
BAPI
Input parameters,
VB
Also,
SAP
self
Screen
Also, even
Web
The page is also just a data collector! (To make some necessary data inspections, they are correct, but even if they are not correct, there is no relationship.
BAPI
Will return error message)
Collection is completed, give it to
BAPI
As a parameter, the rest is
BAPI
Give it, you don't have to manage!
2.
receive
BAPI
The information returned, that is
BAPI
Output parameters and put them
"
translation
"
Improved forms to users.
