SAP system present in customer environment is copy of
original system which is at SAP itself. That means all the
objects present in customer environment are copy of the
object originally created in SAP environment.
So, If we modify copy of object then it is called as repair
and assigned to development task repair. Repair of object is
also called as modification.
Whereas if we modify object in it's original system where it
is actually created may it be SAP system or the objects
created by customer in customer environment. Then such
changes is called as corrections and assigned to task
EDIDC stores control/header record.
EDIDD/EDID4 stores data records.
EDIDS stores status records.
You can use BD87 if you want to reprocess same idoc
number,here it will not generate new idoc number.
suppose there was RFC Issue ,connection got failed then
after rectifying RFC Connection then you can reprocess
same idoc number.
in case data is missing,then you need to WE19 Transaction -
> enter idoc number -> fill the missing data.
just drag the segments ,here you can fill data where ever
If you use WE19 then it creates new idoc ,it gives work
u r trying to generate the idocs with 10
records, and u find only 8 (records) idocs created rest
(records) are missing.
Check with the filter set up for the records for its
receiving partner system(logical system).
Correct the filters then try regenarating the idocs(missing
SAP memory (Global Memory): - is available to a user during
the entire duration of a terminal session. Its contents are
retained across transaction boundaries as well as external
and internal sessions.
The contents of the ABAP/4 memory are retained only during
the lifetime of an external session (see also Organization
of Modularization Units). You can retain or pass data
across internal sessions. The EXPORT TO MEMORY and IMPORT
FROM MEMORY statements allow you to write data to, or read
data from, the ABAP memory.
- communicating between two physically separated systems.
Either SAP to SAP or SAP to Non-SAP ,we use IDOC.
- SAMPLE Scenario is a new custom ALE where the receiver of an
internal service must be able to reverse the invoice receipt,
which will then cancel the applicable billing document
automatically on the service providers system. To avoid the conflicts between two systems.
Table node:tables are dynamic because the table size depend
on the amount of tha data selected at runtime.
Templete node:templetes are static because the no of column
and lines are determind before the actual output.
If you have any error in IDOC u can edit it by using we02 tcode,
after that you can reprocess the corrected IDOC by using bd87
No it is not possible.because vendor number or po numbers
are the uniqe.so it can holds the same vendor or po number
For errors we need to check for the status codes and cming to
debug we can debug our the assingned function module i.e
idoc_input_matmas05 or z(fun module) in case of custom and
while processing in bd87 the complete idoc can be processed
by selecting the option available.